菜单
Produce X/Twitter thread in one of 7 thread types (Thread / Story Thread / Hot Take / How-To Thread / Listicle Thread / Case Study Thread / Daily Tweets batch). Specificity-first, open-curiosity-loop structure, final-tweet CTA. 2-3 threads per week.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Miosa-osa/canopy --skill write-x-thread命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | write-x-thread |
| description | Produce X/Twitter thread in one of 7 thread types (Thread / Story Thread / Hot Take / How-To Thread / Listicle Thread / Case Study Thread / Daily Tweets batch). Specificity-first, open-curiosity-loop structure, final-tweet CTA. 2-3 threads per week. |
| signal | {"mode":"linguistic","genre":"x-thread","type":"inform","format":"markdown","structure":"w-x-thread-7-type","receiver":"X audience + algorithm","receiver_capacity":"low-to-medium"} |
| department | marketing |
| agent_affinity | ["marketing-head","twitter-writer"] |
| required_compartments | {"audience_intelligence_system":50,"offer_architecture":30,"copy_messaging":30} |
| upstream_dependency | content-calendar |
| execution_mode | interactive |
| tier | structured_ai |
| temperature_gate | warm |
| required_tools | ["file_read","file_write"] |
| required_mcps | ["filesystem"] |
| required_integrations | {"social_posting":"twitter-api","scheduling":"buffer-api","analytics":"twitter-analytics"} |
| credentials_required | ["TWITTER_BEARER_TOKEN","TWITTER_API_KEY","TWITTER_API_SECRET","TWITTER_ACCESS_TOKEN","TWITTER_ACCESS_SECRET"] |
| evidence_gate | ["thread_type_selected","hook_tweet_specificity_gte_8","tweet_count_calibrated","final_cta_tweet_present","char_limits_respected","voice_matched","signal_score_gte_0_8"] |
| keywords | ["twitter thread","x thread","write thread","twitter post"] |
| priority | 1 |
| version | 1 |
Produce X/Twitter threads in 7 canonical types. Lineage: Marketing department (7 thread types), direct-response X operators, content-to-conversion bridge applied to async-skim platform.
| # | Type | Use |
|---|---|---|
| 1 | Thread (standard) | General teaching / analysis |
| 2 | Story Thread | Narrative with tension + reveal |
| 3 | Hot Take | Contrarian positioning, polarizing |
| 4 | How-To Thread | Step-by-step actionable |
| 5 | Listicle Thread | Ranked/numbered items |
| 6 | Case Study Thread | Real client result walkthrough |
| 7 | Daily Tweets (batch) | 5-7 single tweets for the week |
Tweet 1 (HOOK) — 280 chars max, 120-200 ideal, earns the open
Tweets 2-N (BODY) — each tweet = 1 idea, paragraph-style, save-optimized
Final tweet (CTA) — single action
Optional: reply-to-thread — link / lead magnet / offer mention
Tweet count calibrated by type:
phrases_to_use across threadSingle action:
First 50 chars visible on many clients. Hook must open in that window.
Save-optimize — threads that get bookmarked get re-surfaced. Structured lists + frameworks + checklists.
One idea per tweet. Don't cram. Threadability = readability.
Polarize for hot takes. Mild takes get zero traction.
Story threads need tension. Arrival → Adversity → Aftermath (Jenny Hoyos 3-A).
No external link in thread body. Link in last tweet or in reply.
Quote-tweet your own thread 24-48h later with a takeaway — 2× reach.
Batch daily tweets on one topic. 5 tweets around one theme > 5 random tweets.
Reply to commenters within 1-2 hours of posting.
Don't over-thread. 15+ tweets = drop-off steep. 7-12 is the sweet spot.
reference/frameworks/primitives/specificity.mdPer calendar brief pillar + stage. Or --type=1-7.
Draft 3-5 variants. Specificity ≥ 8. Select primary.
Per type:
Single action. No stack of asks.
# X Thread — [Creator Brand] — [Topic]
**Calendar Brief ID:** [e.g. W1-TW-1]
**Thread Type:** [1 Thread | 2 Story | 3 Hot Take | 4 How-To | 5 Listicle | 6 Case Study | 7 Daily Tweets]
**Tweet Count:** [N]
**Hook Specificity:** [N/10]
**Publish Time:** [window]
**Version:** 1.0
---
## Thread
### Tweet 1 — HOOK (⬇️ indicator included)
[hook copy — 120-200 chars, visible on first line, ends with "🧵" or "⬇️" or number indicator]
### Tweet 2
[one idea, 180-280 chars]
### Tweet 3
[...]
...
### Final Tweet — CTA
[single action — "Follow for more" | "DM me 'X'" | "Full breakdown: [link]"]
---
## Reply-to-Thread (scheduled T+24-48h)
[takeaway tweet — quotes own thread, drops 1 more insight, re-surfaces]
## Quote-Tweet Plan (T+48-72h)
[quote own hook with takeaway]
---
## Hook Variants (not selected)
1. [variant 1]
2. [variant 2]
## Voice-Match Audit
- phrases_to_use placements: [count]
- Banned vocabulary: [clean]
## Compliance
- [ ] No income guarantees
- [ ] Specificity ≥ 8 on hook
- [ ] FTC disclosure if testimonials
## Publishing Plan
- Publish time: [date + window]
- Reply-to-thread: T+24-48h
- Quote-tweet: T+48-72h
- Engagement block: T+0 to T+90 min
## Repurpose Chain
- Derivative 1: /write-linkedin-post
- Derivative 2: /write-reel (thread main insight as short)
- Derivative 3: /email-sequence (broadcast referencing thread)
---
## Appendix A — Thread structure diagram
[visual of tweet-by-tweet narrative flow]
## Appendix B — Per-tweet save-ability audit
[which tweets most bookmark-able]
/write-linkedin-post — derivative/write-reel — short-form version/email-sequence — broadcast referencereference/frameworks/primitives/specificity.mdreference/canonical/spec/INTEGRATIONS.md (Twitter API)Version 1.0 — 2026-04-19. Cycle 3 Attention — X/Twitter.