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/content-strategy.md
View on GitHub# Content Strategy Reference
> **This file is populated during onboarding** with content pillars, target accounts, and frameworks tailored to the user's niche and goals. Sections marked with `[AUTO-UPDATED]` are refreshed by the Intelligence Update workflow (SKILL.md Workflow 9).
## The 4 Content Pillars
> **Populated during onboarding.** The agent generates 4 pillars based on the user's niche, goals, and content assets. Below is the template structure — the agent replaces these with niche-specific pillars.
### Pillar 1: Portfolio Piece (2-3x/week) -- PRIMARY SHOWCASE
Short demos, screen recordings, screenshots, or case studies of the user's work.
**Structure:**
```
[HOOK -- reference a known brand, surprising stat, or bold claim]
[WHAT -- what you built/did, in 1-2 lines]
[HOW -- 3-4 bullet points of specific details]
[SECRET -- one key insight or technique]
[QUESTION -- invite replies]
[media]
```
**Why it works:** Shows mastery through specifics. Bookmarkable. Gets shared by people who want to reference the technique.
_[Agent: Replace this template with niche-specific examples during onboarding. E.g., for a designer: "design breakdown" posts. For a founder: "product demo" posts. For a DevOps engineer: "infrastructure diagram" posts.]_
---
### Pillar 2: Deep Dive (1-2x/week)
Threads (3-7 tweets) or long-form posts explaining the WHY behind decisions.
**Structure:**
```
Tweet 1: Hook + "Here's the #1 mistake/insight/pattern..." + thread indicator
Tweet 2: The problem explained simply
Tweet 3: The solution/framework
Tweet 4: Proof or code/example
Tweet 5: Takeaway + CTA + question
```
_[Agent: Generate 5-8 topic ideas specific to the user's niche during onboarding.]_
---
### Pillar 3: Process Reveal (1x/week) -- GROWTH HACK
Show HOW you work — your tools, workflow, decision-making process.
**Structure:**
```
[POLARIZING HOOK -- challenge conventional wisdom about how this should be done]
[THE DIFFERENCE -- show your unique approach vs the common approach]
Common way: "[generic approach]"
-> Gets [mediocre result]
Your way: "[specific approach]"
-> Gets this: [proof/media]
[INSIGHT -- why your approach works]
[QUESTION]
```
**Why this pillar grows fastest:** Two audiences care — (1) peers who want to learn your approach, and (2) potential clients/employers who want to hire someone with this process.
_[Agent: Adapt this to the user's specific workflow during onboarding. E.g., AI-directed coding, design system architecture, growth hacking process, etc.]_
---
### Pillar 4: Social Proof Drop (1x/week)
Leverage stats, milestones, and achievements as content.
**Structure:**
```
[MILESTONE -- specific number/achievement]
[CONTEXT -- how you got there, what drove it]
[LESSON -- one insight others can learn from]
[LIST -- top performers or breakdown]
[QUESTION]
```
_[Agent: Populate with the user's actual social proof from onboarding interview. If user has no social proof yet, replace this pillar with a "Learning in Public" pillar.]_
---
## Target Accounts for Engagement
> **Populated during onboarding.** The agent researches the user's niche and identifies accounts to engage with.
### Tier 1 -- High-Follower Creators in Your Niche (borrow their audience)
| Handle | Why | Reply Strategy |
|--------|-----|----------------|
| _[populated during onboarding]_ | _[why this account matters]_ | _[specific approach]_ |
### Tier 2 -- Target Audience (future clients/employers/community)
| Handle | Why | Reply Strategy |
|--------|-----|----------------|
| _[populated during onboarding]_ | _[why this account matters]_ | _[specific approach]_ |
### Tier 3 -- Searches to Monitor Daily
_[populated during onboarding -- search queries to find leads, opportunities, and relevant conversations]_
---
## Reply Framework
### The Anatomy of a High-Value Reply
```
[SPECIFIC OBSERVATION about their post -- shows you actually read it]
[VALUE ADD -- a technique, correction, alternative, or extension]
[SUBTLE PROOF -- mention your experience naturally]
(Optional: [FOLLOW-UP HOOK -- a question or "I've been experimenting with X"])
```
**Good reply example (for a developer niche):**
```
The layout is clean but the scroll animation is doing
too much -- try easing with a cubic-bezier(.22,1,.36,1)
instead of linear for that premium feel.
I ran into the same thing building a similar component
last month. Happy to share the config if you want it
```
This reply: shows expertise (specific technical tip), adds value (actionable fix), includes subtle proof (mentions past experience), and invites follow-up.
_[Agent: Generate 2-3 good reply examples specific to the user's niche during onboarding and add them here.]_
**Bad replies (NEVER DO):**
- "Great post!"
- "This is amazing!"
- "Love this"
- "Facts"
- Any reply under 15 words that adds zero value
---
## Warm DM Templates
> **Populated during onboarding** with templates adapted to the user's goal (client acquisition, job hunting, collaborations, etc.).
### After They Engage With Your Post
```
Hey [name] -- saw you [liked/replied to] my post about [topic].
Noticed you're [building/working on] [their thing]. [Specific observation
about their work + how you could add value].
[Low-commitment CTA -- free audit, quick suggestion, etc.]
```
### After You Engage With Their Post
```
Hey [name] -- was just commenting on your [topic] post.
Your [thing] is [specific compliment]. Quick thought --
[specific value-add suggestion].
[Offer to help -- no strings attached.]
```
### Cold (Use Sparingly)
```
Hey [name] -- I've been following [their thing]
and [specific thing you noticed].
I specialize in [your niche]. [Social proof -- one sentence].
[Would a free [specific deliverable] be useful?]
```
---
## Current Feed Trends [AUTO-UPDATED]
_[populated during intelligence updates]_
### Trending Formats Right Now
_No data yet -- run Intelligence Update to populate._
### Trending Topics Right Now
_No data yet -- run Intelligence Update to populate._
---
## Target Audience Profile [AUTO-UPDATED]
### The "Core Orbit" (Current Engagers)
_No data yet -- run Intelligence Update to populate._
### Potential Follower Analysis
_No data yet -- run Intelligence Update to populate._
### Who We're Targeting
_No data yet -- run Intelligence Update to populate._
### What They Engage With
_No data yet -- run Intelligence Update to populate._
### Content Calendar Alignment
_No data yet -- run Intelligence Update to populate._
_Last updated: never_
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: 322k | 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 |