rabden/X-twitter-social-manager-skill
x-social-manager
FlaggedPersonal X/Twitter social media manager. Use when the user asks to craft, write, review, or optimize X/Twitter posts, threads, replies, or DMs. Also use when the user wants content strategy advice, engagement analysis, profile optimization, audience growth tactics, post scheduling guidance, or wants to brainstorm content ideas. Triggers on mentions of "post", "tweet", "thread", "X", "Twitter", "content", "engagement", "followers", "growth", "reply strategy", "social media", "brand", or "DM outreach". Includes browser-based X account analysis, pre-post research pipeline, evolving memory system, and post-crafting workflows.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 37.6 KB |
| references/algorithm-playbook.md | markdown | 6.1 KB |
| references/branding-strategy.md | markdown | 3.4 KB |
| references/cli-reference.md | markdown | 4.9 KB |
| references/content-planner.md | markdown | 2.7 KB |
| references/content-strategy.md | markdown | 6.4 KB |
| references/growth-strategy.md | markdown | 4.8 KB |
| references/hook-library.md | markdown | 8.3 KB |
| references/media/.gitkeep | other | 0 B |
| references/memory.md | markdown | 4.1 KB |
| references/real-replies-archive.md | markdown | 1.4 KB |
| references/subagent-definitions.md | markdown | 9.1 KB |
| references/user-profile.md | markdown | 3.4 KB |
| references/voice-anti-patterns.md | markdown | 3.9 KB |
references/growth-strategy.md
View on GitHub# X Growth Strategy
> **This file is populated during onboarding** with a tactical playbook customized to the user's niche, goals, follower count, constraints, and time budget. The template below shows the structure — the agent fills it with specific, actionable plans.
## The Diagnosis
_[populated during onboarding -- the agent analyzes the user's current X presence and identifies what's broken. Example structure:]_
<!--
You have a **[type] problem**, not a [type] problem. Your [evidence of skill] confirms this -- [specific proof]. Yet your X presence doesn't reflect any of it.
**Things that are broken right now:**
1. [Problem 1 -- specific to user's situation]
2. [Problem 2 -- specific to user's situation]
3. [Problem 3 -- specific to user's situation]
-->
---
## Phase 0: Foundation (Do This First, Takes 1 Day)
### Profile Overhaul
Your profile is your landing page. Every element must convert a visitor into a follower within 3 seconds.
**Display Name:**
_[populated during onboarding -- format: "Name | Niche Positioning"]_
**Bio:**
_[populated during onboarding -- the agent writes a bio that: (1) States who you help and the outcome, (2) Lists your stack/credentials, (3) Includes social proof, (4) Has a clear CTA]_
**Banner Image:**
_[populated during onboarding -- suggestion for what the banner should show]_
**Pinned Tweet:**
_[populated during onboarding -- what the pinned post should be about]_
---
## Phase 1: The Engagement Engine (Days 1-30)
### Time Budget
_[populated during onboarding -- based on user's stated time budget, split into blocks]_
<!--
| Block | Duration | Activity |
|-------|----------|----------|
| Block 1 | [X] min | Reply to [N] accounts in your target niche |
| Block 2 | [X] min | Create and schedule 1 post |
| Block 3 | [X] min | Reply to comments on your post + engage with [N] more accounts |
-->
### Who to Reply To
_[populated during onboarding -- Tier 1, 2, 3 accounts from content-strategy.md, with specific reply strategies]_
### What a High-Value Reply Looks Like
**DO NOT reply with:** "Great post!" or "This is amazing!" -- these are invisible to the algorithm and look desperate.
**Instead, add genuine value.** Structure:
```
[Specific observation about their post -- proves you read it]
[Value add -- a technique, correction, alternative, or extension]
[Subtle proof -- mention your experience naturally]
```
---
## Phase 2: Content Pillars (Days 1-90)
Your content should rotate between the 4 pillars defined in [content-strategy.md](content-strategy.md). Every post must be **engineered for conversation**.
_[populated during onboarding -- the agent describes each pillar with niche-specific examples, "good post" vs "bad post" comparisons, and hook templates]_
---
## Phase 3: No-Premium Workaround Strategy
_[populated during onboarding -- only included if user doesn't have Premium. References algorithm-playbook.md workarounds with specific tactical steps.]_
---
## Phase 4: Goal-Specific Acquisition Framework (Days 31-90)
_[populated during onboarding -- customized to the user's primary goal]_
<!--
For CLIENT ACQUISITION:
- Warm DM system
- Video audit lead magnet
- Portfolio positioning
For JOB HUNTING:
- Targeted engagement with hiring managers and tech leads
- "Building in public" content that demonstrates hire-ability
- Technical thread strategy for visibility
For AUDIENCE BUILDING:
- Newsletter/product CTA optimization
- Community building tactics
- Collaboration strategy
For THOUGHT LEADERSHIP:
- Contrarian positioning strategy
- Conference/event content leverage
- Media/podcast guest strategy
-->
---
## 90-Day Targets
_[populated during onboarding -- realistic targets based on current follower count, time budget, and niche competitiveness]_
<!--
| Metric | Day 30 | Day 60 | Day 90 |
|--------|--------|--------|--------|
| Followers | [target] | [target] | [target] |
| Avg impressions/post | [target] | [target] | [target] |
| [Goal-specific metric] | [target] | [target] | [target] |
| [Goal-specific metric] | [target] | [target] | [target] |
-->
---
## Key Principles to Remember
- **The Algorithm Cheat Code:** Every post must end with something that FORCES a reply. A question, a hot take, a "what would you do?" -- the reply count IS the reach.
- **The 30-Minute Golden Window:** When you post, stay online and reply to EVERY comment for the first 30 minutes. This triggers the "Author-Engaged Reply" multiplier -- the highest-weighted signal in the Phoenix algorithm.
- **Vector Consistency:** NEVER post about off-topic subjects. Every single post must reinforce your niche positioning. The algorithm maps your account into a vector space -- pollute it and you become invisible.
- **Don't post and ghost.** A post with 50 likes and zero author replies is algorithmically WORSE than a post with 5 likes and 3 back-and-forth conversations. Engagement is not optional -- it's the product.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |