Manage — X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze thei
Instrucciones de origen · Vista previa de solo lectura
name
x-twitter-growth
description
Manage — X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze thei
[{"name":"code_or_task","type":"string","description":"Code snippet, script, or task description to process","required":true}]
output_schema
[{"name":"result","type":"string","description":"Primary output from x twitter growth"}]
X/Twitter Growth Engine
X-specific growth skill. For general social media content across platforms, see social-content. For social strategy and calendar planning, see social-media-manager. This skill goes deep on X.
When to Use This vs Other Skills
Need
Use
Write a tweet or thread
This skill
Plan content across LinkedIn + X + Instagram
social-content
Analyze engagement metrics across platforms
social-media-analyzer
Build overall social strategy
social-media-manager
X-specific growth, algorithm, competitive intel
This skill
Step 1 — Profile Audit
Before any growth work, audit the current X presence. Run scripts/profile_auditor.py with the handle, or manually assess:
Bio Checklist
Clear value proposition in first line (who you help + how)
Specific niche — not "entrepreneur | thinker | builder"
Social proof element (followers, title, metric, brand)
Structure:
- Tweet 1: Hook — must stop the scroll in <7 words
- Tweet 2: Context or promise ("Here's what I learned:")
- Tweets 3-N: One idea per tweet, each standalone-worthy
- Final tweet: Summary + explicit CTA ("Follow @handle for more")
- Reply to tweet 1: Restate hook + "Follow for more [topic]"
Rules:
- 5-12 tweets optimal (under 5 feels thin, over 12 loses people)
- Each tweet should make sense if read alone
- Use line breaks for readability
- No tweet should be a wall of text (3-4 lines max)
- Number the tweets or use "↓" in tweet 1
2. Atomic Tweets (breadth, impression farming)
Formats that work:
- Observation: "[Thing] is underrated. Here's why:"
- Listicle: "10 tools I use daily:\n\n1. X — for Y"
- Contrarian: "Unpopular opinion: [statement]"
- Lesson: "I [did X] for [time]. Biggest lesson:"
- Framework: "[Concept] explained in 30 seconds:"
Rules:
- Under 200 characters gets more engagement
- One idea per tweet
- No links in tweet body (kills reach — put link in reply)
- Question tweets drive replies (algorithm loves replies)
3. Quote Tweets (authority building)
Formula: Original tweet + your unique take
- Add data the original missed
- Provide counterpoint or nuance
- Share personal experience that validates/contradicts
- Never just say "This" or "So true"
4. Replies (network growth, fastest path to visibility)
Strategy:
- Reply to accounts 2-10x your size
- Add genuine value, not "great post!"
- Be first to reply on accounts with large audiences
- Your reply IS your content — make it tweet-worthy
- Controversial/insightful replies get quote-tweeted (free reach)
Posting links directly — Always put links in the first reply, never in the tweet body
Thread tweet 1 is weak — If the hook doesn't stop scrolling, nothing else matters
Inconsistent posting — Algorithm rewards daily consistency over occasional bangers
Only broadcasting — Replies and engagement are 50%+ of growth, not just posting
Generic bio — "Helping people do things" tells nobody anything
Copying formats without adapting — What works for tech Twitter doesn't work for marketing Twitter
Related Skills
social-content — Multi-platform content creation
social-media-manager — Overall social strategy
social-media-analyzer — Cross-platform analytics
content-production — Long-form content that feeds X threads
copywriting — Headline and hook writing techniques
Why This Skill Exists
Manage — X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement.
What If Fails
If this skill fails to produce the expected output: (1) verify input completeness, (2) retry with more specific context, (3) fall back to the parent workflow without this skill.
