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-planner.md
View on GitHub# Content Planner
Automated pipeline for planning, queuing, and scheduling posts. Run this workflow when the user asks to plan content, or proactively suggest it during engagement sessions.
**Core principle:** 60% community/engagement posts, 40% self-showcase posts. Never post more than 2 self-promo posts in a row. It's okay to copy/adapt viral formats that are working for others.
## The Planning Pipeline
### Step 1: Feed Scan (5 min)
Scan the algorithmic feed for trending topics, viral formats, and high-engagement posts.
```bash
twitter feed --json -n 30 --filter
```
### Step 2: Competitor Analysis (5 min)
Fetch recent posts from Tier 1 accounts (listed in content-strategy.md).
```bash
twitter user-posts [TIER1_HANDLE] --max 10 -c --json
```
### Step 3: Trend Research (5 min)
Search for trending and niche-relevant topics.
```bash
twitter search "[niche topic]" -t Latest --max 20 -c --json
```
### Step 4: Reply Opportunities
Draft substantive replies for high-value posts found during the scan.
### Step 5: Post Drafting
Draft 3-5 posts ensuring the 60/40 engagement-to-showcase split. Each post needs:
- Post type and content pillar
- Full text with `[N/280]` character count
- Hook type (from hook-library.md)
- Media requirements (video, image, visual hook image, none)
- First reply text (for links and extra context)
- Hashtags (1-3)
- Strategic reasoning
### Step 6: Scheduling
**User's timezone:** _[set from user-profile.md during onboarding]_
**Optimal Posting Windows (adjust to user's timezone):**
| Slot | UTC Time | Best For |
|------|----------|----------|
| Morning overlap | 13:00-15:00 | US morning + Europe afternoon |
| Afternoon peak | 17:00-19:00 | US afternoon, peak browsing |
| Weekend Saturday | 14:00-16:00 | Less competition, good reach |
| Weekend Sunday | 16:00-18:00 | Evening engagement spike |
**Scheduling Rules:**
- Never schedule 2 showcase posts back-to-back
- Space posts at least 4-6 hours apart
- Prefer the user's historically best-performing time slots (check memory.md)
- Account for the user's availability during the 30-minute golden window
---
## Planned Posts Queue
_[posts are added here by the Content Planner workflow and removed/marked as posted after execution]_
<!--
### Planned Post #N
- **Status:** draft / approved / posted / skipped
- **Type:** [post type from content pillars]
- **Scheduled:** [YYYY-MM-DD HH:MM timezone]
- **Text:** [full post text] [N/280]
- **Media:** [path to media file, "visual hook image needed", or "none"]
- **First Reply:** [link + context for first reply]
- **Hashtags:** [#tag1 #tag2]
- **Strategic Reasoning:** [why this post, why this time, what gap it fills]
- **Post Result:** (filled after posting)
- Tweet ID: [id]
- Views: [N]
- Likes: [N]
- Replies: [N]
-->
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 |