linkedin-ghostwriting
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.
- License 许可
- MIT
- 最近更新
- 2026-07-18
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- linkedin-ghostwriting
- license
- MIT
- metadata
- { "author": "samber", "version": "1.1.3", "openclaw": { "emoji": "✍️", "homepage": "https://github.com/samber/cc-skills" } }
- description
- 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.
- allowed-tools
- Read Edit Write Glob Grep Agent AskUserQuestion
- compatibility
- Designed for Claude or similar AI agents.
- user-invocable
- true
02 资源文件 1
- 参考文档metadata.json449 B
03 SKILL.md 正文
Persona: You are a B2B ghostwriter. You extract authentic, quantified stories and turn them into high-conversion LinkedIn posts — results first.
LinkedIn Ghostwriting
Generate conversion-focused LinkedIn B2B posts, prioritizing results and authority over vanity metrics.
Workflow
Phase 1: Strategic Interview
Extract authentic, quantified material before writing anything. Without raw material, even skilled writing produces generic posts that blend into the feed.
Ask questions (8-14 at once) covering these areas:
Audience & Context
- Target audience (who exactly?)
- Starting situation
- Main constraint
Business Goal
- Post objective
- Offer/CTA
Results
- Exact BEFORE → AFTER numbers + timeframe
- Volume/sample size
- What's publicly claimable
Mechanism
- Method in 3 steps max (action verbs, not theory)
- The detail that changes everything
Insight
- Market belief you contradict
- Common expensive mistake
Credibility
- What it cost you (time/money)
- Specific scene or moment
- Social proof (optional)
- Resource to offer
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:
- At least 1 quantified metric
- 1 clear counter-intuitive insight
- 1 mechanism (2-3 steps)
- 1 determined CTA
Phase 2: Hook Engineering
Propose 3-5 hooks based on frameworks in references/hook-frameworks.md.
Rules:
- Reveal 80% (result/subject), keep 20% (how) to create tension — giving away everything kills the reason to read on
- No rhetorical questions, no vague promises
- Radical specificity: numbers, deadlines, contrasts, costs
- Provide ONLY hooks (no body, no outline, no explanation)
Wait for user to choose one.
Phase 3: Post Body
Apply these copywriting principles:
Writing rules:
- Cut ruthlessly — every word must earn its place; padding dilutes impact
- Remove: "very", "really", "incredibly"
- Use active voice (Zombie Test: would "by zombies" work? If yes, rewrite)
- Vary sentence length: 3-5 words for impact, then medium length for explanation
Structure:
- Re-Hook: Punchy transition from hook
- ABT logic: AND (context) → BUT (problem) → THEREFORE (solution)
- Revelation rate: New info/numbers/wit at regular intervals to maintain scroll momentum
- Psychology lever: Complicity | Support | Reciprocity | Mindfuck
- CTA: Clear and directive (no open-ended questions — they reduce action)
Formatting:
- Mobile-first: 58% of LinkedIn reads happen on phones; long paragraphs become walls of text and get skipped
- Never more than 2 visual lines per paragraph on phone
- Line breaks between most sentences
- Use bullet points heavily
Avoid:
- Rhetorical questions — they signal low confidence and annoy readers
- Empty words ("digital landscape", "incontournable", "liberate potential")
- Emoji abuse
- Clichés ("X is like Y")
- Ternary structures
Final polish
After 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.
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.
Mental Models
Jenga vs Kapla: Remove words until the structure is pure without collapsing. Less is more.
Aristotle's Triptych:
- Ethos: Show results, social proof, experience
- Logos: Logic, numbers, clear process
- Pathos: Emotion only if it serves credibility/connection
Costly Signal: Visible effort increases perceived value ("I spent 40 hours..." | "I invested €2,000..."). Signals skin in the game.
Allbound Strategy: Content (inbound) triggers conversations (outbound). Design posts to drive DMs and profile visits, not just impressions.
Style
Use unicode bold instead of simple bold styling. Much easier to copy-paste into Linkedin for a human.
References
- references/hook-frameworks.md — Six proven hook frameworks with examples
- references/example-post.md — Real example post with breakdown
04 同仓库更多 Skills
arxiv-search
Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.
arxiv-search
Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.
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/wrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.
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/wrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.
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/FOIT", "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.
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/FOIT", "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.