social-copy
Use when the user wants to create social media posts or launch copy for a feature, product change, PR, or announcement - generates platform-specific copy for Twitter/X, LinkedIn, and other platforms
AlemTuzlak · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add AlemTuzlak/skills --skill social-copy技能说明
name: social-copy description: Use when the user wants to create social media posts or launch copy for a feature, product change, PR, or announcement - generates platform-specific copy for Twitter/X, LinkedIn, and other platforms
Social Copy Writer
Generate platform-specific social media copy from code changes, marketing briefs, blog posts, or feature descriptions. Each platform gets copy tailored to its rules, audience behavior, and algorithm.
Writing rule (non-negotiable): never use em-dashes (— or –). Use a hyphen - instead. Applies to every platform's copy.
Input Resolution
Resolve the argument (if provided) in this order:
- Path to an existing marketing brief file (
.mdcontaining "Executive Summary" or "Key Messages") → marketing brief - Path to an existing blog post file (
.mdwith blog post structure) → blog post - Matches GitHub URL or
#\d+pattern → PR - Contains
...or..→ git ref range - Resolves to existing file/directory → codebase feature
- Otherwise → freeform text
If no argument is provided, ask: "What should I write social copy for? You can provide a marketing brief, blog post, PR URL/number, git ref range, file/directory path, or just describe the feature."
If multiple interpretations match, confirm with the user.
Process Flow
digraph social_copy {
rankdir=TB;
"Resolve input" [shape=box];
"Phase 1: Discovery" [shape=box];
"Phase 2: Configure" [shape=box];
"Phase 3: Write" [shape=box];
"Phase 4: Review" [shape=box];
"Approved?" [shape=diamond];
"Phase 5: Output" [shape=box];
"Resolve input" -> "Phase 1: Discovery";
"Phase 1: Discovery" -> "Phase 2: Configure";
"Phase 2: Configure" -> "Phase 3: Write";
"Phase 3: Write" -> "Phase 4: Review";
"Phase 4: Review" -> "Approved?" ;
"Approved?" -> "Phase 3: Write" [label="revisions"];
"Approved?" -> "Phase 5: Output" [label="yes"];
}
Do NOT skip phases. Ask questions at a natural pace. Don't overwhelm, but don't artificially slow things down either. If the user answers multiple questions at once, accept bundled answers and skip ahead.
If the user says "just pick defaults", "you choose", or similar, pick reasonable defaults based on context, state what you chose, and ask for a single confirmation before proceeding.
Never assume without confirming.
Phase 1: Discovery
Step 1 - Analyze the input
| Input type | What to read |
|---|---|
| Marketing brief | Extract problem statement, value prop, audience, key messages, competitive positioning. Skip to Step 3. Still do Step 2 if brief lacks product context. |
| Blog post | Extract headline, key points, audience, CTA. Skip to Step 3. Still do Step 2 if blog post lacks product context. |
| PR | Diff, PR description, review comments, commit messages (gh pr view, gh pr diff). For large PRs (20+ files), focus on user-facing changes. |
| Git refs | git diff and git log between refs. For large ranges, prioritize commit messages and user-facing changes. |
| Codebase feature | Read the specified files/directories. |
| Freeform text | Parse the user's description. If it lacks specifics (no feature name, no value prop, no context), ask the user to provide more detail or point to a specific file/PR. Fall back to open-ended questions only if they can't. |
User-facing changes include: new features, UI changes, API changes, performance improvements, bug fixes, and documentation updates. Internal changes include: refactors, test additions, CI changes, and dependency bumps. When uncertain, list what you found and ask the user which are relevant.
Error handling:
ghnot available → inform user, suggestgh auth login, offer alternative input- Invalid PR/ref → ask user to verify
- File not found → ask for correct path
Step 2 - Read broader product context
Read if they exist: README, docs/, package.json (or equivalent).
If nothing found, ask: "I couldn't find product context in the repo. Can you briefly describe the product and who it's for?"
Step 3 - Present understanding
"Here's what I'll base the social copy on:"
- Feature A - short description
- Feature B - short description
"Anything to add, remove, or correct?"
Do NOT proceed until the user confirms scope.
Phase 2: Configuration
Ask these questions:
Q1 - Platforms: "I'll generate copy for Twitter/X and LinkedIn by default. Want to add any other platforms?" (Reddit, Hacker News, Discord, Mastodon, Bluesky, etc.)
If the user adds platforms not covered by existing platform reference files, adapt the copy using your knowledge of that platform's conventions.
Q2 - Tone: Read existing repo content (README, docs, blog posts, social links) to detect the product's voice. Then confirm with presets:
"Based on your existing content, the tone seems [e.g. conversational and developer-focused]. Should I match that, or would you prefer a different direction? Some common options:"
- Professional/thought-leadership
- Casual/conversational
- Witty/playful
- Technical/precise
- Founder-voice/authentic
If no existing content to analyze, present the presets directly.
Q3 - Launch format: "Do you want a single post per platform or a full launch sequence?"
- Single post - one post per platform
- Launch sequence - teaser (pre-launch), announcement (launch day), follow-up (post-launch)
Q4 - CTA: Infer the most appropriate call to action from context:
- Open source → star the repo, contribute, try it out
- SaaS → sign up, start free trial
- Feature update → try the new feature, read the docs
- Library/SDK → install it, check the docs
"I'd suggest the CTA be: [inferred CTA]. Want to go with that or something different?"
Phase 3: Write
Read the platform reference files before writing. Platform rules are in the platforms/ directory relative to this skill file. The skill-loading system should inject these files into