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/memory.md
View on GitHub# Memory -- X Account Evolution Log
> This is a living document. Append new entries after every significant interaction. Never delete old entries.
> **This file is initialized during onboarding and updated continuously by the agent.**
---
## Account Snapshot
- **Handle:** _[populated during onboarding]_
- **Followers:** _[populated during onboarding]_
- **Premium:** _[populated during onboarding]_
- **Phase:** _[populated during onboarding -- e.g., "Zero-to-One (pre-500 followers)"]_
- **Start Date:** _[populated during onboarding]_
---
## Voice & Reply Architecture
<!-- Auto-populated during onboarding by analyzing the user's real replies. MANDATORY READ before writing ANY reply. Also read voice-anti-patterns.md EVERY TIME. -->
### Vocabulary Fingerprint
**Words/phrases the user naturally uses:**
_[populated during onboarding -- extracted from real replies]_
**Words/phrases the user NEVER uses:**
_[populated during onboarding -- inferred from reply analysis + user interview]_
### Structural Patterns
_[populated during onboarding -- sentence length, capitalization habits, punctuation style, line break usage, emoji usage, @mention format, grammar quirks]_
### Reply Archetypes (with real examples)
_[populated during onboarding -- 5-7 archetypes extracted from the user's actual replies, each with a label, description, and 2-3 real examples]_
### Mandatory Pre-Reply Check
Before finalizing ANY reply, the agent MUST read [voice-anti-patterns.md](voice-anti-patterns.md) and run the Voice Verification Checklist. If any check fails, rewrite from scratch.
---
## Environment Status
- **twitter-cli:** _[set during prerequisites check]_
- **Sub-agents:** _[set during sub-agent setup]_
- **Auth method:** _[set during prerequisites check]_
- **Last verified:** _[set during prerequisites check]_
---
## Post Performance Log
_[entries added automatically after each post -- format below]_
<!--
### [Date] -- [Post Title/Topic] ([Post Type])
- **Topic:** [what the post was about]
- **Format:** [text-only / image+text / video / thread]
- **Hook used:** [which hook framework from hook-library.md]
- **Stats:**
- Likes: [N]
- Retweets: [N]
- Replies: [N]
- Bookmarks: [N]
- Views: [N]
- **Engagement Rate:** [calculated: (likes+replies+retweets+bookmarks)/views x 100]
- **Lesson:** [what worked or didn't]
-->
---
## Engagement Tracking
_[entries added after engagement sessions -- format below]_
<!--
### [Date] ([Session Type])
- **Accounts engaged with:** [@handle1, @handle2, ...]
- **Replies sent:**
- @handle: [brief description]. [ID: tweet_id]
- **Strategy used:** [which archetypes, which approach]
- **Notable interactions:** [any brand/creator responses, new connections]
-->
---
## Intelligence Update Log
_[entries added after each intelligence update -- format below]_
<!--
### [Date] -- [Update Type: Mini/Standard/Deep]
- **Key Findings:**
- [finding 1]
- [finding 2]
- **Files Updated:** [list of files modified]
- **Audience Segment:** [primary segments engaging]
-->
---
## Growth Milestones
| Date | Followers | Notes |
|------|-----------|-------|
| _[onboarding date]_ | _[starting count]_ | Initial onboarding |
---
## Lessons Learned
_[entries added as patterns emerge -- format below]_
<!--
- **[Topic]:** [lesson learned from data]
-->
---
## Competitor Watchlist
_[populated during intelligence updates -- format below]_
<!--
| Account | Niche | Avg Engagement | Hook Style | Content Gap |
|---------|-------|---------------|------------|-------------|
| @handle | [niche] | [rate] | [style] | [gap we can fill] |
-->
---
## Audience Intelligence
_[populated during intelligence updates -- format below]_
<!--
### Audience Segments
| Segment | % of Engagers | Preferred Content | Peak Activity |
|---------|--------------|-------------------|---------------|
| [segment] | [%] | [type] | [time] |
-->
---
## Client/Connection Leads
_[entries added when potential leads are identified -- format below]_
<!--
| Handle | Type | Status | Last Contact | Notes |
|--------|------|--------|-------------|-------|
| @handle | [client/employer/collaborator] | [prospect/contacted/replied/converted] | [date] | [notes] |
-->
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 |