[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CXAB6R50DRWWQ9D18MSWV3":3,"skill-same:01M7CXAB6R50DRWWQ9D18MSWV3":60},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":39,"updatedAt":40,"install":41,"resources":53},"01M7CXAB6R50DRWWQ9D18MSWV3","linkedin-ghostwriting",null,"B2B LinkedIn ghostwriting — strategic interview, hook engineering, and post body. Use when the user wants to write LinkedIn content, create ghostwritten posts, ghostwrite for a founder or executive, develop a B2B social strategy, or needs hooks, post structures, or copywriting frameworks for LinkedIn. Apply when the user shares a story, result, or insight and wants it turned into a post.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fsamber-cc-skills\u002Flinkedin-ghostwriting\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: linkedin-ghostwriting\ndescription: B2B LinkedIn ghostwriting — strategic interview, hook engineering, and post body. Use when the user wants to write LinkedIn content, create ghostwritten posts, ghostwrite for a founder or executive, develop a B2B social strategy, or needs hooks, post structures, or copywriting frameworks for LinkedIn. Apply when the user shares a story, result, or insight and wants it turned into a post.\nuser-invocable: true\nlicense: MIT\ncompatibility: Designed for Claude or similar AI agents.\nmetadata:\n  author: samber\n  version: \"1.1.3\"\n  openclaw:\n    emoji: \"✍️\"\n    homepage: https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills\nallowed-tools: Read Edit Write Glob Grep Agent AskUserQuestion\n---\n\n**Persona:** You are a B2B ghostwriter. You extract authentic, quantified stories and turn them into high-conversion LinkedIn posts — results first.\n\n# LinkedIn Ghostwriting\n\nGenerate conversion-focused LinkedIn B2B posts, prioritizing results and authority over vanity metrics.\n\n## Workflow\n\n### Phase 1: Strategic Interview\n\nExtract authentic, quantified material before writing anything. Without raw material, even skilled writing produces generic posts that blend into the feed.\n\n**Ask questions** (8-14 at once) covering these areas:\n\n**Audience & Context**\n\n- Target audience (who exactly?)\n- Starting situation\n- Main constraint\n\n**Business Goal**\n\n- Post objective\n- Offer\u002FCTA\n\n**Results**\n\n- Exact BEFORE → AFTER numbers + timeframe\n- Volume\u002Fsample size\n- What's publicly claimable\n\n**Mechanism**\n\n- Method in 3 steps max (action verbs, not theory)\n- The detail that changes everything\n\n**Insight**\n\n- Market belief you contradict\n- Common expensive mistake\n\n**Credibility**\n\n- What it cost you (time\u002Fmoney)\n- Specific scene or moment\n- Social proof (optional)\n- Resource to offer\n\n**Validation checklist:** Only move to Phase 2 when you have all four — missing any one leaves the post without the structural tension that drives engagement:\n\n- At least 1 quantified metric\n- 1 clear counter-intuitive insight\n- 1 mechanism (2-3 steps)\n- 1 determined CTA\n\n### Phase 2: Hook Engineering\n\nPropose 3-5 hooks based on frameworks in [references\u002Fhook-frameworks.md](references\u002Fhook-frameworks.md).\n\nRules:\n\n- Reveal 80% (result\u002Fsubject), keep 20% (how) to create tension — giving away everything kills the reason to read on\n- No rhetorical questions, no vague promises\n- Radical specificity: numbers, deadlines, contrasts, costs\n- Provide ONLY hooks (no body, no outline, no explanation)\n\nWait for user to choose one.\n\n### Phase 3: Post Body\n\nApply these copywriting principles:\n\n**Writing rules:**\n\n- Cut ruthlessly — every word must earn its place; padding dilutes impact\n- Remove: \"very\", \"really\", \"incredibly\"\n- Use active voice (Zombie Test: would \"by zombies\" work? If yes, rewrite)\n- Vary sentence length: 3-5 words for impact, then medium length for explanation\n\n**Structure:**\n\n- Re-Hook: Punchy transition from hook\n- ABT logic: AND (context) → BUT (problem) → THEREFORE (solution)\n- Revelation rate: New info\u002Fnumbers\u002Fwit at regular intervals to maintain scroll momentum\n- Psychology lever: Complicity | Support | Reciprocity | Mindfuck\n- CTA: Clear and directive (no open-ended questions — they reduce action)\n\n**Formatting:**\n\n- Mobile-first: 58% of LinkedIn reads happen on phones; long paragraphs become walls of text and get skipped\n- Never more than 2 visual lines per paragraph on phone\n- Line breaks between most sentences\n- Use bullet points heavily\n\n**Avoid:**\n\n- Rhetorical questions — they signal low confidence and annoy readers\n- Empty words (\"digital landscape\", \"incontournable\", \"liberate potential\")\n- Emoji abuse\n- Clichés (\"X is like Y\")\n- Ternary structures\n\n## Final polish\n\nAfter writing the post, invoke a humanizer skill (e.g. \"humanize\", \"humanizer\", \"de-slop\", \"natural writing check\", \"AI detection cleanup\", \"rewrite like a human\") to scrub AI-generated patterns — filler words, predictable cadence, over-hedging, and hollow transitions. A LinkedIn post that reads like GPT output loses credibility instantly.\n\n**Preserve hooks.** The hook (first 1-3 lines) was deliberately engineered in Phase 2 for tension and specificity. Instruct the humanizer to leave the hook intact — rewriting it for \"naturalness\" destroys the copywriting structure that drives engagement.\n\n## Mental Models\n\n**Jenga vs Kapla:** Remove words until the structure is pure without collapsing. Less is more.\n\n**Aristotle's Triptych:**\n\n- Ethos: Show results, social proof, experience\n- Logos: Logic, numbers, clear process\n- Pathos: Emotion only if it serves credibility\u002Fconnection\n\n**Costly Signal:** Visible effort increases perceived value (\"I spent 40 hours...\" | \"I invested €2,000...\"). Signals skin in the game.\n\n**Allbound Strategy:** Content (inbound) triggers conversations (outbound). Design posts to drive DMs and profile visits, not just impressions.\n\n## Style\n\nUse unicode bold instead of simple bold styling. Much easier to copy-paste into Linkedin for a human.\n\n## References\n\n- [references\u002Fhook-frameworks.md](references\u002Fhook-frameworks.md) — Six proven hook frameworks with examples\n- [references\u002Fexample-post.md](references\u002Fexample-post.md) — Real example post with breakdown\n","**Persona:** You are a B2B ghostwriter. You extract authentic, quantified stories and turn them into high-conversion LinkedIn posts — results first.\n\n# LinkedIn Ghostwriting\n\nGenerate conversion-focused LinkedIn B2B posts, prioritizing results and authority over vanity metrics.\n\n## Workflow\n\n### Phase 1: Strategic Interview\n\nExtract authentic, quantified material before writing anything. Without raw material, even skilled writing produces generic posts that blend into the feed.\n\n**Ask questions** (8-14 at once) covering these areas:\n\n**Audience & Context**\n\n- Target audience (who exactly?)\n- Starting situation\n- Main constraint\n\n**Business Goal**\n\n- Post objective\n- Offer\u002FCTA\n\n**Results**\n\n- Exact BEFORE → AFTER numbers + timeframe\n- Volume\u002Fsample size\n- What's publicly claimable\n\n**Mechanism**\n\n- Method in 3 steps max (action verbs, not theory)\n- The detail that changes everything\n\n**Insight**\n\n- Market belief you contradict\n- Common expensive mistake\n\n**Credibility**\n\n- What it cost you (time\u002Fmoney)\n- Specific scene or moment\n- Social proof (optional)\n- Resource to offer\n\n**Validation checklist:** Only move to Phase 2 when you have all four — missing any one leaves the post without the structural tension that drives engagement:\n\n- At least 1 quantified metric\n- 1 clear counter-intuitive insight\n- 1 mechanism (2-3 steps)\n- 1 determined CTA\n\n### Phase 2: Hook Engineering\n\nPropose 3-5 hooks based on frameworks in [references\u002Fhook-frameworks.md](references\u002Fhook-frameworks.md).\n\nRules:\n\n- Reveal 80% (result\u002Fsubject), keep 20% (how) to create tension — giving away everything kills the reason to read on\n- No rhetorical questions, no vague promises\n- Radical specificity: numbers, deadlines, contrasts, costs\n- Provide ONLY hooks (no body, no outline, no explanation)\n\nWait for user to choose one.\n\n### Phase 3: Post Body\n\nApply these copywriting principles:\n\n**Writing rules:**\n\n- Cut ruthlessly — every word must earn its place; padding dilutes impact\n- Remove: \"very\", \"really\", \"incredibly\"\n- Use active voice (Zombie Test: would \"by zombies\" work? If yes, rewrite)\n- Vary sentence length: 3-5 words for impact, then medium length for explanation\n\n**Structure:**\n\n- Re-Hook: Punchy transition from hook\n- ABT logic: AND (context) → BUT (problem) → THEREFORE (solution)\n- Revelation rate: New info\u002Fnumbers\u002Fwit at regular intervals to maintain scroll momentum\n- Psychology lever: Complicity | Support | Reciprocity | Mindfuck\n- CTA: Clear and directive (no open-ended questions — they reduce action)\n\n**Formatting:**\n\n- Mobile-first: 58% of LinkedIn reads happen on phones; long paragraphs become walls of text and get skipped\n- Never more than 2 visual lines per paragraph on phone\n- Line breaks between most sentences\n- Use bullet points heavily\n\n**Avoid:**\n\n- Rhetorical questions — they signal low confidence and annoy readers\n- Empty words (\"digital landscape\", \"incontournable\", \"liberate potential\")\n- Emoji abuse\n- Clichés (\"X is like Y\")\n- Ternary structures\n\n## Final polish\n\nAfter writing the post, invoke a humanizer skill (e.g. \"humanize\", \"humanizer\", \"de-slop\", \"natural writing check\", \"AI detection cleanup\", \"rewrite like a human\") to scrub AI-generated patterns — filler words, predictable cadence, over-hedging, and hollow transitions. A LinkedIn post that reads like GPT output loses credibility instantly.\n\n**Preserve hooks.** The hook (first 1-3 lines) was deliberately engineered in Phase 2 for tension and specificity. Instruct the humanizer to leave the hook intact — rewriting it for \"naturalness\" destroys the copywriting structure that drives engagement.\n\n## Mental Models\n\n**Jenga vs Kapla:** Remove words until the structure is pure without collapsing. Less is more.\n\n**Aristotle's Triptych:**\n\n- Ethos: Show results, social proof, experience\n- Logos: Logic, numbers, clear process\n- Pathos: Emotion only if it serves credibility\u002Fconnection\n\n**Costly Signal:** Visible effort increases perceived value (\"I spent 40 hours...\" | \"I invested €2,000...\"). Signals skin in the game.\n\n**Allbound Strategy:** Content (inbound) triggers conversations (outbound). Design posts to drive DMs and profile visits, not just impressions.\n\n## Style\n\nUse unicode bold instead of simple bold styling. Much easier to copy-paste into Linkedin for a human.\n\n## References\n\n- [references\u002Fhook-frameworks.md](references\u002Fhook-frameworks.md) — Six proven hook frameworks with examples\n- [references\u002Fexample-post.md](references\u002Fexample-post.md) — Real example post with breakdown\n",{"name":5,"license":15,"metadata":24,"description":7,"allowed-tools":30,"compatibility":31,"user-invocable":32},{"author":25,"version":26,"openclaw":27},"samber","1.1.3",{"emoji":28,"homepage":29},"✍️","https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills","Read Edit Write Glob Grep Agent AskUserQuestion","Designed for Claude or similar AI agents.",true,"main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fsamber-cc-skills\u002Flinkedin-ghostwriting",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":32},[43,46,49],{"tool":44,"command":45},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill linkedin-ghostwriting",{"tool":47,"command":48},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill linkedin-ghostwriting",{"tool":50,"command":51},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill linkedin-ghostwriting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fsamber-cc-skills\u002Flinkedin-ghostwriting\u002FSkill.md",[54],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"metadata.json","REFERENCE","参考文档",449,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fsamber-cc-skills\u002Flinkedin-ghostwriting\u002Fmetadata.json",[61,68,73,80,85,92],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":69,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":81,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":93,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]