$npx -y skills add Affitor/affiliate-skills --skill twitter-thread-writerWrite X/Twitter threads that get bookmarked, shared, and drive affiliate clicks. Use this skill when the user asks about writing Twitter threads, X threads, tweet threads for affiliate marketing, or says "write a thread about X", "Twitter thread promoting X", "X thread for affili
| 1 | # Twitter Thread Writer |
| 2 | |
| 3 | Write X/Twitter threads that deliver genuine value, build authority, and naturally |
| 4 | recommend affiliate products without feeling like ads. The best affiliate threads |
| 5 | get bookmarked for the insights and clicked for the product recommendation. |
| 6 | |
| 7 | ## Stage |
| 8 | |
| 9 | This skill belongs to Stage S2: Content |
| 10 | |
| 11 | ## When to Use |
| 12 | |
| 13 | - User wants to promote an affiliate product on X/Twitter |
| 14 | - User wants to build an audience on X while monetizing with affiliate links |
| 15 | - User has expertise to share and wants to weave in a product recommendation |
| 16 | - User asks how to write threads that convert without being spammy |
| 17 | - User wants content that compounds (bookmarks → future impressions) |
| 18 | |
| 19 | ## Input Schema |
| 20 | |
| 21 | ``` |
| 22 | { |
| 23 | product: { |
| 24 | name: string # (required) "ConvertKit" |
| 25 | description: string # (optional) What it does |
| 26 | url: string # (optional) Affiliate link |
| 27 | reward_value: string # (optional) For context only — never shown in thread |
| 28 | } |
| 29 | thread_angle: string # (optional, default: auto) See Thread Frameworks below |
| 30 | expertise_area: string # (optional) Creator's area of authority — "email marketing", "SaaS growth" |
| 31 | audience: string # (optional) "founders", "freelancers", "content creators" |
| 32 | tone: string # (optional, default: "direct") "direct" | "educational" | "storytelling" | "contrarian" |
| 33 | tweet_count: number # (optional, default: 8) Number of tweets in thread: 5-15 |
| 34 | personal_story: string # (optional) Real experience or result to anchor the thread |
| 35 | cta_style: string # (optional, default: "soft") "soft" | "direct" | "question" |
| 36 | } |
| 37 | ``` |
| 38 | |
| 39 | ## Workflow |
| 40 | |
| 41 | ### Step 1: Research the Product and Angle |
| 42 | |
| 43 | Use `web_search "[product name] best features use cases"` and |
| 44 | `web_search "[product name] vs [competitor]"` to find: |
| 45 | - The 2-3 strongest use cases (thread body material) |
| 46 | - The problem it solves that X audiences care about |
| 47 | - Any recent updates, launches, or news (recency boosts engagement) |
| 48 | - Real user testimonials or case study numbers (third-party proof) |
| 49 | |
| 50 | Also search `web_search "site:twitter.com [product name] affiliate"` to see what |
| 51 | existing threads look like — then do something different or better. |
| 52 | |
| 53 | ### Step 2: Select the Thread Framework |
| 54 | |
| 55 | | Framework | Structure | Best For | |
| 56 | |-----------|-----------|----------| |
| 57 | | **Lessons Learned** | "I used [product] for X months. Here's what I learned:" → 7 insights → CTA | Tools you've genuinely used | |
| 58 | | **Problem → Solution** | Hook pain → Agitate it → Introduce solution → Show how it solves each pain → CTA | High-awareness problems | |
| 59 | | **Contrarian Take** | "Everyone says [common advice]. I disagree. [product] changed my mind." | Standing out in crowded niches | |
| 60 | | **Numbers Story** | "From [before metric] to [after metric] using [product]. Here's how:" → step-by-step → CTA | When you have real results | |
| 61 | | **How-to Tutorial** | "How to [achieve outcome] with [product] in [timeframe]:" → step-by-step → CTA | Educational, drives bookmarks | |
| 62 | | **Tool Stack** | "My [role] tool stack in 2024: Thread on each → [product] gets its own deep-dive tweet → CTA | Multi-product threads | |
| 63 | | **Myth Busting** | "5 myths about [problem space] — and what actually works:" → each myth → [product] as the solution | High engagement, saves | |
| 64 | |
| 65 | Auto-select based on: |
| 66 | - Has personal experience → Numbers Story or Lessons Learned |
| 67 | - No personal experience → How-to Tutorial or Problem → Solution |
| 68 | - Large audience, strong takes → Contrarian Take |
| 69 | - Beginner-friendly product → How-to Tutorial |
| 70 | |
| 71 | ### Step 3: Write the Hook Tweet (Tweet 1) |
| 72 | |
| 73 | The hook tweet determines if anyone reads tweet 2. It must: |
| 74 | - Promise a specific, tangible outcome ("how I 3x'd my email open rate") |
| 75 | - Or state a bold, curiosity-generating claim ("most email marketing advice is wrong") |
| 76 | - Or open a story loop ("6 months ago I had 400 email subscribers. Today I have 12,000.") |
| 77 | - End with a signal that a thread follows: "A thread:" or "Here's how:" or "Thread 🧵" |
| 78 | |
| 79 | Never start with: "I want to share...", "In this thread...", "Have you ever..." |
| 80 | Never use buzzwords as hooks: |