メニュー
Orchestrator for the 3-article content pipeline — runs research phase, spawns parallel article sub-agents, creates Typefully drafts. Use when running the full content pipeline (usually via cron at 3am).
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/exiao/skills --skill content-pipelineコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Use when generating hooks, headlines, titles, and scroll-stopping openers for content. Also use when analyzing viral posts, Reels, TikToks, YouTube Shorts, or successful social examples to extract reusable hook patterns and improve hook guidance.
Verify a code change actually works by building/running the app and observing it at its real surface (CLI, API, UI, library, agent), capturing runtime evidence rather than trusting tests. Make sure to use this skill whenever the user has changed code and wants to know it works, is about to merge/push and wants confidence, says "did this actually work", "verify this works", "prove it works", "confirm the change", "make sure it works", wants runtime evidence, or is re-running tests / importing-and-calling just to check behavior, even if they never say the word "verify". When in doubt after any code change, reach for this. For post-deploy production health checks use verify-deploy; for static correctness/quality review use simplify or code-review.
Test an interactive lesson/course (or any "instructions to an AI" skill) by self-play. An agent plays BOTH the instructor following the lesson script AND a calibrated student persona, producing full turn-by-turn transcripts of every lesson, then publishes the raw transcripts to a single static page. Use when asked to "run lesson transcripts", "test the course end to end", "self-play the lessons", "publish raw test transcripts", "walk a synthetic student through every lesson", or to QA an interactive-instruction skill by actually running it rather than just reviewing findings. Distinct from dogfood and adversarial-ux-test (web-app browser QA) and synthetic-userstudies (findings plus a few cherry-picked transcripts). This one captures the COMPLETE run of every lesson and ships them all raw.
SOC 職業分類に基づく
SKILL.md を表示中
| name | content-pipeline |
| description | Orchestrator for the 3-article content pipeline — runs research phase, spawns parallel article sub-agents, creates Typefully drafts. Use when running the full content pipeline (usually via cron at 3am). |
Produces 3 article drafts per run: research once, then spawn 3 parallel sub-agents (one per article). Sub-agents handle their own skill reads. This orchestrator only handles the research phase and final reporting.
Do NOT publish anything. Everything stays as drafts.
~/clawd/memory/content-published.md — topics already covered are off-limitsbird tweets --user $TWITTER_USER -n 30 --plain — note angles the author published in the last 30 daysweb_fetch https://$SUBSTACK_URL — find recent post titles~/clawd/memory/content-published.mdRead ~/marketing/WRITING-STYLE.md first.
bird. Note which topics/angles got most engagement (likes, replies, retweets)./grok-search with --x to find what's trending in the author's niches (AI, investing, indie dev, fintech)./last30days across YouTube, X, Reddit, and Substack to find viral formats, hooks, and topics with momentum.Topics should come from what's actually resonating on social, not from a fixed theme list. Look for:
Not every article needs to be about Bloom. Pick topics because they're genuinely interesting and the author has something real to say. Bloom integration only if it's natural and adds to the piece.
Pick topics where the author has unique credibility. Avoid angles anyone could write. Validate with X engagement data from Step 1a.
For each topic: quick web search for what's already been written. Find the contrarian angle or data point competitors missed.
Write all findings to ~/marketing/substack/drafts/[YYYY-MM-DD]-research.md:
Spawn 3 sub-agents in parallel using sessions_spawn, one per topic. Each sub-agent receives:
Topic: [topic]
Positioning angle: [angle from research]
X engagement insight: [what angle resonated with the author's audience]
Output directory: ~/marketing/substack/drafts/[slug]/
Your job:
1. Read ~/marketing/WRITING-STYLE.md
2. Run /hooks — generate 5 options, pick strongest → hooks.md
3. Run /outline-generator → outline.md
4. Run /writer → draft.md (must pass "only the author could write this" test: use specific numbers, named frameworks, personal experience. Reference Bloom only if naturally relevant to the topic.)
5. Run /editor-in-chief — max 5 iterations → editing-log.md + draft-final.md
6. Generate a hero image → hero.png
7. Write LinkedIn post directly → linkedin-post.md
- Re-read ~/marketing/WRITING-STYLE.md kill phrases list before writing
- Write a native LinkedIn post from draft-final.md. Do NOT reframe into "here's what most people get wrong" or "X isn't Y, it's Z" patterns. Lead with the most specific, surprising fact or data point from the article. Let the story carry the reader — no interpretive sentences telling them what to feel.
- Run /evaluate-content on the post (Voice + Leanness scores only). If either scores below 4/5, rewrite and re-check. Max 2 revision passes.
- Save final version to linkedin-post.md (post body only — no metadata headers)
8. Write X thread → x-thread.md
- Run writer to create 5 standalone tweets from draft-final.md and sequence them as a thread.
- No promotional framing, no article links in thread body (link goes in reply)
9. Format for Substack → substack-ready.md
Do NOT publish. Do NOT send messages unless blocked.
~/marketing/substack/drafts/[slug]/
hooks.md # 5 options + winner
outline.md
draft.md
editing-log.md
draft-final.md
substack-ready.md
hero.png
x-thread.md
linkedin-post.md
After all 3 sub-agents complete, for each article save a Substack draft using the Substack skill with profile=clawd.
NEVER click Publish. Draft only.
Steps per article:
~/marketing/substack/drafts/[slug]/substack-ready.md for title, subtitle, and bodybrowser action=open targetUrl="https://$SUBSTACK_URL/publish/post" profile=clawdhero.png as the cover imageAfter Substack drafts are saved, create Typefully drafts for each article:
IMPORTANT: Save as UNSCHEDULED drafts only. Do NOT schedule or publish anything.
# X thread draft — unscheduled draft only
cd ~/clawd/skills/typefully && node scripts/typefully.js drafts:create $TYPEFULLY_SOCIAL_SET_ID \
--platform x --text "$(cat ~/marketing/substack/drafts/[slug]/x-thread.md)"
# LinkedIn draft — unscheduled draft only
node scripts/typefully.js drafts:create $TYPEFULLY_SOCIAL_SET_ID \
--platform linkedin --text "$(cat ~/marketing/substack/drafts/[slug]/linkedin-post.md)"
Do NOT send via the message tool. Just output the summary as your reply. Cron delivery handles routing.
Include: