threads-pipeline

Use when the user wants to write a Threads post end-to-end starting from raw dump (no pre-existing angle) — dump-first workflow with 10 steps: dump → main thread → interview supplement → diagnosis → narrative draft → hooks → user calibration → finalize → anti-template → versions. Triggers: user says 「我有東西想寫但還沒想清楚」/「幫我從原始素材寫文」/「跑寫文工作流」/「我要寫 Threads 但沒 angle」, dumps raw material without a pre-locked angle. PREREQUISITE: none (Step 1 accepts raw dump). Do NOT use when user has a locked angle.md — use threads-write-post v2 (which starts from angle). Do NOT use for Stage 0 angle decisions if user is still unsure — use threads-angle-gate first.

Use when the user wants to write a Threads post end-to-end after the angle is locked — pick framework, plan thread skeleton, map algorithm mechanisms, design interaction, draft, review, publish. Triggers: user says 「幫我寫貼文」/「從 angle 寫到發文」/「跑 advisor pipeline」/「我有 angle.md 了下一步是」, asks to continue from an existing drafts/*.angle.md, or wants the full Stage 1→7 workflow. PREREQUISITE: angle.md must exist (run `threads-angle-gate` first if it doesn't). Do NOT use for Stage 0 angle decisions — that is `threads-angle-gate`'s job. Do NOT use for pure CLI ops (publish/list/insights) — that is `threads-cli`. Do NOT use for analytics-only queries — that is `threads-advisor analyze`.

Use when the user wants to decide the sharpness / angle of a Threads post BEFORE drafting, or when a draft reads like event recounting without a clear reason to share. Triggers: user says 「幫我想切入點」/「這篇要怎麼切」/「我想寫 X 但不知道怎麼下筆」, pastes raw material asking to turn it into a post, or shows a draft they themself say feels flat / 沒重點 / 沒銳利點. Do NOT use for revising drafts that already have a clear angle—use `threads-advisor review` instead. Do NOT use for pure info queries or historical insight analysis.

How to use the `threads` CLI and `threads-advisor` tools to operate the user's Threads account — publish posts, reply, list/search posts, fetch insights, delete posts, analyze performance, review drafts. Use this skill whenever the user asks to post on Threads, check their Threads analytics/insights, list or search their posts, reply to a post, delete a post, analyze which posts perform best, review a draft before posting, or any Threads account operation. Also use when the user mentions 'threads' CLI, 'advisor', Threads API operations, content strategy, or wants to interact with their Meta Threads account programmatically.

Threads API CLI — publish posts, reply, publish thread chains. Supports Agent mode via --confirm --yes.