菜单
Use when the user wants to announce a product launch or new feature. Triggers: "HN Show post", "announce feature", "product launch post", "announce on HN", "write launch announcement", "post on HN", "Product Hunt post", "IndieHackers post", "GitHub launch".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | launch-post |
| description | Use when the user wants to announce a product launch or new feature. Triggers: "HN Show post", "announce feature", "product launch post", "announce on HN", "write launch announcement", "post on HN", "Product Hunt post", "IndieHackers post", "GitHub launch". |
Read .agents/content-context.md first (if it exists).
Write launch announcements for developer channels. Different channels need different framing.
Title formula: Show HN: [Product Name] – [One-sentence value proposition]
Rules:
Body structure (first comment on your own submission):
After approval: offer to run /publish-hn to generate the submitlink.
Tagline: ~60 chars, action-oriented, no superlatives.
Formula: [Product] – [Verb] [Outcome] for [Audience]
Example: content-ops – Cross-post Markdown articles to dev.to and Hashnode
Maker comment (≤800 chars):
Timing: post Tue–Thu at 12:01 AM PST (leaderboard resets at midnight PST). Pre-launch: 2–4 weeks of teaser content; aim for 300+ waitlist before launch day.
Subreddit tiers:
Rules:
Headline formula: [Specific number] + [Transformation] + [Timeframe]
Example: $1,200 MRR in 90 days building in public — what worked and what didn't
awesome-* listsTitle: specific and descriptive, no clickbait.
Body structure:
Set canonical_url to your own domain when cross-posting. Publish on your domain first, then cross-post.
/publish-hn to generate the submitlink.Use when the user wants to set up or update their content profile. Also use when the user says "my blog is about", "content profile", "set up content context", or "who am I writing for". Stores context as .agents/content-context.md — read by all other content-ops skills first.
Use when the user wants content ideas or a backlog. Triggers: "content ideas", "what to write next", "build backlog", "ideas from changelog", "what should I post about", "content calendar".
Use before publishing any article. Triggers: "check article", "preflight", "validate post", "is this ready to publish", "QA my post", "pre-publish check". Run this before distribute or any publish command.
Use when the user wants feedback on marketing copy, headlines, or landing page text. Triggers: "edit landing page", "improve headline", "copy feedback", "review this copy", "is this headline good", "landing page copy review".
Use when the user wants to publish an article to multiple platforms at once. Triggers: "publish article", "distribute to platforms", "send to devto and hashnode", "cross-post", "publish everywhere", "distribute my post".
Use when the user wants to write a welcome sequence or email drip campaign. Triggers: "welcome sequence", "newsletter drip", "onboarding emails", "email series", "welcome email". Note: generates drafts only — no sending, no API.