[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QJ1Z3NSKMHQ3SM2WW6BE5W":3,"skill-same:01M6QJ1Z3NSKMHQ3SM2WW6BE5W":76},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":14,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6QJ1Z3NSKMHQ3SM2WW6BE5W","linkedin-content",null,"Use when someone wants to write, edit, or lint a LinkedIn post — a story, how-to, opinion piece, carousel script, video script, or poll — or wants an article, talk, or transcript repurposed into posts. Triggers on \"write a LinkedIn post\", \"is this hook any good\", \"review my post\", \"turn this into LinkedIn posts\", \"carousel\", \"what format should this be\". Lints posts 0-100 on mechanics, hook, integrity, and accessibility; picks the format the material actually supports; and splits long sources into standalone units with a reuse ledger.","Tashima-Tarsh\u002FDisha6.6","Tashima-Tarsh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269906498?v=4","01M6PBH98X03XERH0HFT4PFB1P","NITISH KUMAR","01M6PBH9DA0M6KM3Z12P848F0K",0,"MIT","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Flinkedin-content\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"content","linkedin","linkedin content","standalone","review","carousel","posts","linkedin post","sources","video script","article","mechanics","good","edit","write","marketing","how","Video","integrity","transcript","2026-11-10 10:12:30",false,"---\nname: linkedin-content\ndescription: Use when someone wants to write, edit, or lint a LinkedIn post — a story, how-to, opinion piece, carousel script, video script, or poll — or wants an article, talk, or transcript repurposed into posts. Triggers on \"write a LinkedIn post\", \"is this hook any good\", \"review my post\", \"turn this into LinkedIn posts\", \"carousel\", \"what format should this be\". Lints posts 0-100 on mechanics, hook, integrity, and accessibility; picks the format the material actually supports; and splits long sources into standalone units with a reuse ledger.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-08-25\n---\n\n# LinkedIn Content — format, draft, lint\n\nThe post is not the deliverable; the specific thing only this person can say is. The scripts\nhandle format choice, mechanical faults, and de-duplication. The interesting part — what\nactually happened and what it cost — comes from the user, and cannot be generated.\n\n## Workflow\n\n**1. Check the brief exists.** If there is no positioning brief, offer `linkedin-strategy`\nfirst as a question. Posts without pillars are noise. Never chain silently.\n\n**2. Pick the format from the material, not from fashion.**\n\n```bash\npython3 scripts\u002Fformat_picker.py --goal authority --material data --material tutorial \\\n  --minutes 120 --output human\n```\n\nExit 0 recommends \u002F 2 asks when the top two are within a point (tie-break on which one they\nwould enjoy making — the one they repeat beats the one that scores higher once) \u002F 3 no fit,\ngo get material. It refuses video with no camera and no footage, and a poll with no real\ndecision behind it.\n\n**3. Draft.** Interview for specifics before writing a line: the number, the mistake, the\nsentence someone said. Then write to the fold — **the first ~140 characters are the whole\npost for most readers**, and a sentence must complete inside them.\n\n**4. Lint before it ships.**\n\n```bash\npython3 scripts\u002Fpost_linter.py --input draft.md --has-image --output human\n```\n\nExit 0 SHIP \u002F 2 REVISE (or any blocking finding) \u002F 3 REWRITE. Blocking findings have named\nconsequences: over the 3,000-character cap; engagement bait, named as demoted content in the\nProfessional Community Policies; Unicode pseudo-bold, which screen readers announce as\nmathematical symbols and search does not index as words. Two passes is normal; the stop\ncondition is exit 0 or a stated decision to accept a warning.\n\n**5. Repurposing.** Split a source and keep the ledger — it prevents the specific recurring\nfailure of the same idea going out three times over eight months. Commit it alongside the\nsource; it is project state, not a cache. Every unit is source material, not a post: add the\nsentence only the author can write — what it cost, or what they would do differently.\n\n```bash\npython3 scripts\u002Frepurpose_splitter.py --input talk.md --ledger .linkedin-ledger.json --output human\npython3 scripts\u002Frepurpose_splitter.py --input talk.md --ledger .linkedin-ledger.json --record 2 --posted-on 2026-08-25\n```\n\n## Rules\n\n- **Never fabricate a number, a client, a result, or a quote.** Not one, not as a placeholder.\n- **Write to the mobile fold.** A sentence completes before character 140.\n- **Links in the first comment**, and say so in the post.\n- **No Unicode pseudo-bold, ever.** It is an accessibility failure, not a style choice.\n- **Alt text on every image; captions on every video.** LinkedIn does not add them for you.\n- **No engagement bait.** Ask the question the post actually earned.\n- **The author reads every line before it ships.** They are the author of record.\n\n## Scripts\n\n| Script | Role |\n|---|---|\n| [`scripts\u002Fpost_linter.py`](scripts\u002Fpost_linter.py) | 0-100 across mechanics \u002F hook \u002F integrity \u002F accessibility; blocking findings for the cap, bait, and pseudo-bold. |\n| [`scripts\u002Fformat_picker.py`](scripts\u002Fformat_picker.py) | Ranks nine native formats against goal, material, and minutes; refuses camera-less video and decision-less polls. |\n| [`scripts\u002Frepurpose_splitter.py`](scripts\u002Frepurpose_splitter.py) | Splits a source into standalone units, scores them, and skips anything already in the reuse ledger. |\n\n## References and assets\n\n- [`references\u002Fhook_and_fold_mechanics.md`](references\u002Fhook_and_fold_mechanics.md) — the first 140 characters, and the openers to delete on sight (7 sources)\n- [`references\u002Fpost_formats_canon.md`](references\u002Fpost_formats_canon.md) — what each native format is good at, and the carousel trap (7 sources)\n- [`references\u002Frepurposing_discipline.md`](references\u002Frepurposing_discipline.md) — standalone units, the reuse ledger, source types and their risks (7 sources)\n- [`references\u002Faccessibility_and_inclusion.md`](references\u002Faccessibility_and_inclusion.md) — pseudo-bold, alt text, captions, and why they are blocking (7 sources)\n\n- [`assets\u002Fpost_templates.md`](assets\u002Fpost_templates.md) — five worked post shapes with the hook already doing its job\n- [`assets\u002Fexample_post.md`](assets\u002Fexample_post.md) — a post that passes the linter, annotated\n\n## Distinct from\n\n- **`linkedin-strategy`** — decides what the posts are about. This writes them.\n- **`linkedin-engagement`** — comments and DMs. A comment is a different craft with a\n  different budget; it lives there.\n- **`marketing-skill\u002Fcopywriting` \u002F `content-humanizer`** — general copy and de-AI passes.\n  Reach for those for tone; this one owns LinkedIn's mechanics and its accessibility floor.\n\n---\n\n**Version:** 1.0.0\n","# LinkedIn Content — format, draft, lint\n\nThe post is not the deliverable; the specific thing only this person can say is. The scripts\nhandle format choice, mechanical faults, and de-duplication. The interesting part — what\nactually happened and what it cost — comes from the user, and cannot be generated.\n\n## Workflow\n\n**1. Check the brief exists.** If there is no positioning brief, offer `linkedin-strategy`\nfirst as a question. Posts without pillars are noise. Never chain silently.\n\n**2. Pick the format from the material, not from fashion.**\n\n```bash\npython3 scripts\u002Fformat_picker.py --goal authority --material data --material tutorial \\\n  --minutes 120 --output human\n```\n\nExit 0 recommends \u002F 2 asks when the top two are within a point (tie-break on which one they\nwould enjoy making — the one they repeat beats the one that scores higher once) \u002F 3 no fit,\ngo get material. It refuses video with no camera and no footage, and a poll with no real\ndecision behind it.\n\n**3. Draft.** Interview for specifics before writing a line: the number, the mistake, the\nsentence someone said. Then write to the fold — **the first ~140 characters are the whole\npost for most readers**, and a sentence must complete inside them.\n\n**4. Lint before it ships.**\n\n```bash\npython3 scripts\u002Fpost_linter.py --input draft.md --has-image --output human\n```\n\nExit 0 SHIP \u002F 2 REVISE (or any blocking finding) \u002F 3 REWRITE. Blocking findings have named\nconsequences: over the 3,000-character cap; engagement bait, named as demoted content in the\nProfessional Community Policies; Unicode pseudo-bold, which screen readers announce as\nmathematical symbols and search does not index as words. Two passes is normal; the stop\ncondition is exit 0 or a stated decision to accept a warning.\n\n**5. Repurposing.** Split a source and keep the ledger — it prevents the specific recurring\nfailure of the same idea going out three times over eight months. Commit it alongside the\nsource; it is project state, not a cache. Every unit is source material, not a post: add the\nsentence only the author can write — what it cost, or what they would do differently.\n\n```bash\npython3 scripts\u002Frepurpose_splitter.py --input talk.md --ledger .linkedin-ledger.json --output human\npython3 scripts\u002Frepurpose_splitter.py --input talk.md --ledger .linkedin-ledger.json --record 2 --posted-on 2026-08-25\n```\n\n## Rules\n\n- **Never fabricate a number, a client, a result, or a quote.** Not one, not as a placeholder.\n- **Write to the mobile fold.** A sentence completes before character 140.\n- **Links in the first comment**, and say so in the post.\n- **No Unicode pseudo-bold, ever.** It is an accessibility failure, not a style choice.\n- **Alt text on every image; captions on every video.** LinkedIn does not add them for you.\n- **No engagement bait.** Ask the question the post actually earned.\n- **The author reads every line before it ships.** They are the author of record.\n\n## Scripts\n\n| Script | Role |\n|---|---|\n| [`scripts\u002Fpost_linter.py`](scripts\u002Fpost_linter.py) | 0-100 across mechanics \u002F hook \u002F integrity \u002F accessibility; blocking findings for the cap, bait, and pseudo-bold. |\n| [`scripts\u002Fformat_picker.py`](scripts\u002Fformat_picker.py) | Ranks nine native formats against goal, material, and minutes; refuses camera-less video and decision-less polls. |\n| [`scripts\u002Frepurpose_splitter.py`](scripts\u002Frepurpose_splitter.py) | Splits a source into standalone units, scores them, and skips anything already in the reuse ledger. |\n\n## References and assets\n\n- [`references\u002Fhook_and_fold_mechanics.md`](references\u002Fhook_and_fold_mechanics.md) — the first 140 characters, and the openers to delete on sight (7 sources)\n- [`references\u002Fpost_formats_canon.md`](references\u002Fpost_formats_canon.md) — what each native format is good at, and the carousel trap (7 sources)\n- [`references\u002Frepurposing_discipline.md`](references\u002Frepurposing_discipline.md) — standalone units, the reuse ledger, source types and their risks (7 sources)\n- [`references\u002Faccessibility_and_inclusion.md`](references\u002Faccessibility_and_inclusion.md) — pseudo-bold, alt text, captions, and why they are blocking (7 sources)\n\n- [`assets\u002Fpost_templates.md`](assets\u002Fpost_templates.md) — five worked post shapes with the hook already doing its job\n- [`assets\u002Fexample_post.md`](assets\u002Fexample_post.md) — a post that passes the linter, annotated\n\n## Distinct from\n\n- **`linkedin-strategy`** — decides what the posts are about. This writes them.\n- **`linkedin-engagement`** — comments and DMs. A comment is a different craft with a\n  different budget; it lives there.\n- **`marketing-skill\u002Fcopywriting` \u002F `content-humanizer`** — general copy and de-AI passes.\n  Reach for those for tone; this one owns LinkedIn's mechanics and its accessibility floor.\n\n---\n\n**Version:** 1.0.0\n",{"name":5,"license":15,"metadata":49,"description":7},{"author":50,"updated":51,"version":52,"category":39},"Alireza Rezvani",1787616000000,"1.0.0","main","0da4485785ee599388900be50db1635489d53056",".agents\u002Fskills\u002Flinkedin-content","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6","https:\u002F\u002Fdisha6.6.thenitishkr.in\u002F","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh","www.thenitishkr","thenitishkr | AI • Cyber-security • Research\r\n","2026-11-08 03:33:25",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add Tashima-Tarsh\u002FDisha6.6 --skill linkedin-content",{"tool":68,"command":69},"bunx","bunx skills add Tashima-Tarsh\u002FDisha6.6 --skill linkedin-content",{"tool":71,"command":72},"pnpm","pnpm dlx skills add Tashima-Tarsh\u002FDisha6.6 --skill linkedin-content","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Flinkedin-content\u002FSKILL.md",true,[],[77,107,130,157,182,206],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":88,"publishedAt":44},"01M6QRD07D4TGNDK6VJ4EHF8BV","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[83],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[89,90,91,43,92,93,94,41,95,96,97,98,99,100,101,102,103,104,105,106],"youtube full","youtube","full","search","monitoring","data","Audio","list","files","do","get","age","trigger","URL","for","browsing","request","youtube transcripts",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":44},"01M6QRCJ3112VYPA97YG7KGMC2","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[114,115,116,117,92,24,118,119,120,121,122,123,38,124,125,126,127,128,129,103],"twitter","x twitter growth","growth","research","engineering","plan","web search","competitors","analyze","engine","strategy","use","platform","grow","posting","competitive",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":139,"publishedAt":44},"01M6QRBN3EHQNJY42RERP7A149","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[136],{"categoryNo":137,"categoryName":138,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000023","Skill与智能体开发",[140,38,141,142,143,144,145,146,125,147,148,53,149,150,151,152,153,154,155,156],"write a skill","github","create","https","productivity","matt pocock","direct","example","build","new skill","structure","new agent","resources","with","tree","progressive disclosure","author",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":44},"01M6QRB6G8P33PNGAF9Y69EJ9T","wrap-up","Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says \"wrap up\", \"close this out\", \"what do I own now\", \"give me the summary\", \"recap the agent\", or when the orchestrator routes phase=wrap-up. primitives_inventory.py tables everything owned (agent, environment, session, memory, outcome, deployment); overview_page.py regenerates a self-contained .\u002Fmy-agent\u002Fagent-overview.html; upgrade_suggester.py ranks the next moves from recorded deferrals plus standing hardening steps. Companion to run-without-you; the last stop before phase=done.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[164,165,166,167,168,169,170,171,172,125,173,98,174,175,176,177,178,179,180,181],"wrap up","up","wrap","gemini","deployment","run","file","hardening","closeout","stop","upgrade","founder","close","companion","you","tables","directions","phase",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":189,"publishedAt":44},"01M6QRA5AYC1RBFZ39GTWGS3N8","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[188],{"categoryNo":137,"categoryName":138,"taxonomyType":86,"taxonomyTypeDesc":87},[190,191,192,193,194,142,169,195,196,197,198,199,38,200,97,201,202,203,204,205],"workflow","workflow builder","builder","design","workflows","code","orchestrate","pipeline","loop","multi-agent","context","across","fresh","scripts","judge","claude code workflow",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":212,"publishedAt":44},"01M6QR7QMCZESKQA0ERW1E657M","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[28,213,214,215,216,217,218,219,220,198,221,222,223,224,225,226,99,227,228,181],"weekly review","weekly","deterministic scripts","reflect","feeds","inventory","open","team","projects","project-management","scanner","conversation","back","project","sprint","cadence"]