メニュー
Use when the user wants to plan and execute a multi-platform launch. Triggers: "launch plan", "launch sequence", "launch checklist", "multi-platform launch", "coordinate launch", "launch timeline".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
| name | launch-sequence |
| description | Use when the user wants to plan and execute a multi-platform launch. Triggers: "launch plan", "launch sequence", "launch checklist", "multi-platform launch", "coordinate launch", "launch timeline". |
Read .agents/content-context.md first (if it exists).
Orchestrate a multi-platform launch across three tiers: a short spike, community seeding, and long-tail distribution. Each tier has different mechanics, timing, and content formats.
| Tier | Channels | Window | Goal |
|---|---|---|---|
| Spike | Product Hunt, Show HN, BetaList | 24–72 h | Burst visibility, initial users |
| Community | IndieHackers, Reddit, Twitter #buildinpublic | Weeks 1–4 | Qualified audience, trust |
| Long-tail | dev.to / Hashnode, directories, awesome-* lists | Months–years | Compounding organic traffic |
Do not treat all three tiers as simultaneous. Spike content burns fast; long-tail content compounds slowly.
| Day | Action |
|---|---|
| -14 | Publish teaser on Twitter/Bluesky, open waitlist, start IH presence |
| -7 | "I'm building X" post on IndieHackers, Reddit r/SideProject |
| -3 | BetaList submission (7-day lead time); finalize PH assets (social preview, maker comment) |
| 0 | Product Hunt at 12:01 AM PST; Show HN at 8–10 AM PT (same day or next) |
| +1 | Reply to all PH and HN comments; post Twitter/Bluesky launch thread |
| +3 | "I built X" article on dev.to / Hashnode (link back to PH/HN threads) |
| +7 | Post-mortem / lessons-learned post on IndieHackers with real numbers |
| +14 | Submit to directories (BetaPage, Uneed, Lobste.rs, etc.) |
| +28 | Submit to awesome-* lists; write SEO-targeted follow-up article |
Product Hunt
Show HN
IndieHackers
dev.to / Hashnode
canonical_url set to own domainGitHub
launch-post skillsocial-thread skill.content-ops-state.json with platform statuses.