菜单
Turns messy project notes into high-signal LinkedIn posts for AI, research, startup, hackathon, education, or technical audiences. Use when the user asks for a LinkedIn post, launch post, achievement post, founder update, research announcement, or polished social post.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Compiles a vague project idea into agent-ready work - a sprint spec, a contract of testable assertions, and an ordered task list with acceptance criteria. Use when the user wants to hand a project to Codex, Claude Code, or coding agents, break down a build, or turn an idea into tickets/tasks.
Creates a new Claude Skill to fable-mythos standard - a tight SKILL.md plus eval cases and an example. Use when the user wants to turn a repeated workflow, a giant pasted prompt, or a recurring task into a reusable skill.
Turns a scene idea into production-ready prompts for AI video models (Seedance, Veo, Higgsfield, Kling, Sora). Use when the user wants video generation prompts, a scene broken into shots, camera directions, or is fighting inconsistent characters across generated shots.
Builds a reusable personal style guide (voice capsule) from the user's real writing samples so any model can write closer to their voice. Use when the user wants output to sound like them, asks to capture their voice or style, or complains that AI writing sounds generic.
Repairs a Claude Skill after a bad output by identifying the exact failure, patching SKILL.md, and adding a regression test. Use when a skill output is generic, wrong, overhyped, off-format, or fails the user's expectations.
| name | linkedin-signal-posts |
| description | Turns messy project notes into high-signal LinkedIn posts for AI, research, startup, hackathon, education, or technical audiences. Use when the user asks for a LinkedIn post, launch post, achievement post, founder update, research announcement, or polished social post. |
Turn messy project notes into a sharp LinkedIn post that builds credibility and gives the reader one useful idea. The post must sound like a real builder, not a corporate announcement.
Read examples.md in this skill's folder before writing — the voice lives there, not in adjectives.
Work with what you're given. If BOTH proof and audience are missing, ask one batched question for them — never more than one round. Never invent metrics, users, or traction the notes don't contain.
Explicit user requests beat style rules. If the user asks for something the rules forbid (e.g. "start with Thrilled to announce"), do it their way, offer one alternative hook, and don't lecture.
[The post]
1–3 different first lines.
Unsupported, vague, or overhyped parts — or "clean".
Compressed to under 80 words.
