strategy
Skill3 starsChanged 7 months agoMITView on GitHub
Plan weekly or monthly X content strategy. Use when the user wants to plan their content calendar, set growth goals, build a content pipeline, or think strategically about their X presence.
We split this skill into the rules it gives an agent
8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
If the user provides their X username or profile URL, read their profile to auto-assess current state instead of relying on self-reported …
- Very specific: line 27
Use WebFetch to read https://x.com/[username] — extract bio, follower/following counts, recent post previews, and pinned post.
- Distinctive: line 53
Every account needs 3-5 content pillars — recurring themes the audience expects:
- Distinctive: line 102
No self-promotional replies — add genuine value
- Distinctive: line 110
Don't worry about analytics yet — focus on content quality and consistency
- Distinctive: line 114
Start tracking which formats perform best
- Distinctive: line 117
Start building email list or external presence to bootstrap engagement
- Distinctive: line 123
Start an evergreen queue for your best content (OpenTweet)
“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Content Strategy Planning
Build a comprehensive X content strategy aligned with the Phoenix algorithm and the user's goals.
Input
The user provides:
- Niche/topic area — what they post about
- Current state — follower count, typical engagement, posting frequency
- Their X profile URL or username — read their profile and recent posts directly
- Goals — growth targets, audience building, product promotion, thought leadership
- Constraints — time available, content resources, posting schedule limitations
- Timeframe — weekly plan, monthly plan, or long-term roadmap
Process
Step 0 — Read User's X Profile (if available)
If the user provides their X username or profile URL, read their profile to auto-assess current state instead of relying on self-reported data:
Use WebFetch to read https://x.com/[username] — extract bio, follower/following counts, recent post previews, and pinned post.
For deeper analysis (engagement metrics on recent posts, analytics data), suggest running /analyze recent which uses chrome for authenticated access.
This replaces the need for the user to manually report their follower count, posting frequency, and engagement levels.
Step 1 — Assess Current State
Understand where the user is:
Account Stage:
| Stage | Followers | Strategy Focus |
| Launch | 0-100 | Reply farming, community building, 1 quality post/day |
| Growth | 100-1K | Content consistency, thread expertise, niche authority |
| Scale | 1K-10K | Content pillars, collaborations, repurposing pipeline |
| Authority | 10K+ | Thought leadership, selective posting, community building |
Content Audit:
- What formats have they tried?
- What's worked best? (ask for data or review)
- What's their authentic voice/personality?
- What unique knowledge or experience do they have?
Step 2 — Define Content Pillars
Every account needs 3-5 content pillars — recurring themes the audience expects:
Pillar 1: [Primary expertise — what you know best]
Pillar 2: [Practical value — tips, tutorials, how-tos]
Pillar 3: [Perspective — opinions, takes, industry commentary]
Pillar 4: [Personal/Build-in-public — behind the scenes, journey]
Pillar 5: [Community — responses, curations, collaborations]The mix should be approximately:
- 40% expertise + practical value (builds authority)
- 30% perspective (drives engagement)
- 20% personal/build-in-public (builds connection)
- 10% community engagement posts (builds network)
Step 3 — Build the Calendar
Weekly Template:
MONDAY — [Pillar: Perspective]
Post: Observation or hot take about the niche
Time: 9-10 AM ET
Reply goal: Engage with 10+ posts in niche before posting
TUESDAY — [Pillar: Expertise]
Thread: Deep dive or tutorial
Time: 8-9 AM ET
Reply goal: Respond to all comments within 1 hour
WEDNESDAY — [Pillar: Practical Value] ← Peak day
Post: Quick tip, code snippet, or actionable insight
Time: 9 AM ET
Reply goal: Maximum engagement — clear schedule for 1 hour post-publish
THURSDAY — [Pillar: Community]
Quote tweet or collaboration with another account
OR Poll related to niche topic
Time: 10-11 AM ET
FRIDAY — [Pillar: Build-in-Public]
Post: Weekly progress update, lesson learned, or behind-the-scenes
Time: 10 AM ET (lighter engagement expected — that's OK)Daily Non-Negotiables (20-30 min):
- Reply to all comments on your posts (75-150× multiplier)
- Engage with 10-15 posts from accounts in your niche
- No self-promotional replies — add genuine value
Step 4 — Growth Tactics by Stage
Launch (0-100 followers):
- Reply to 20-30 posts daily in target niche (visibility building)
- One quality post per day (compound effect over 30 days)
- Find 10 accounts in your niche at similar size — engage consistently
- Don't worry about analytics yet — focus on content quality and consistency
Growth (100-1K):
- 3-5 posts per week with at least 1 thread
- Start tracking which formats perform best
- Reply farming before every post (15-30 min)
- Repost/quote tweet others' content with added insight
- Start building email list or external presence to bootstrap engagement
Scale (1K-10K):
- Establish a consistent posting rhythm your audience expects
- Repurpose top content (use /repurpose skill)
- Collaborate: quote tweet, co-threads, or shout-outs with similar-sized accounts
- Start an evergreen queue for your best content (OpenTweet)
- Analyze weekly: what's working, what's not (use /review skill)
Authority (10K+):
- Quality > quantity — selective posting with high impact
- Launch content series (recurring threads on a specific day)
- Build community through conversations, not broadcasts
- Mentor smaller accounts (creates loyalty and network effects)
Step 5 — Set Measurable Goals
Define 30-day targets:
| Metric | Current | Target | Strategy |
| Followers | ? | ? | [specific growth tactics] |
| Avg impressions/post | ? | ? | [content quality improvements] |
| Avg replies/post | ? | ? | [CTA optimization] |
| Engagement rate | ? | ? | [format and timing optimization] |
| Posts per week | ? | ? | [consistency target] |
Step 6 — Output
Present:
- Account assessment — Current stage and key observations
- Content pillars — 3-5 defined themes with examples
- Weekly calendar — Specific posting plan with times
- Growth tactics — Stage-appropriate strategies
- 30-day goals — Measurable targets
- First week action items — 5-7 specific things to do this week
- Content ideas — 10 specific post ideas across the pillars
Rules
- Strategy must be sustainable — don't plan more than the user can maintain
- Quality always trumps quantity
- Consistency matters more than perfection
- Adjust strategy based on data — review weekly with /review skill
- The algorithm rewards authentic expertise — don't fake authority in areas you don't know
Other versions21 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 21
- menkesu/awesome-pm-skills★ 441same name
- andreaskelm/pm-brain★ 234same name
- thesun4sky/jobstack★ 50same name
- rainday/smart-blog-skills★ 35same name
- galiprandi/job-seeker★ 33same name
- skyf0xx/gambit★ 26same name
- superuser-pal/awesome-second-brain★ 14same name
- BhaskarManam/pstack★ 4same name
- EmanueleMinotto/minottobot★ 4same name
- dkyazzentwatwa/skill_starter_pack★ 2same name
11 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use north-star, brand-voice and 4 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
UMwaiSkillnorth-star
Evaluate whether current work serves the project's ultimate goal. Scores branches, goals, and commits against declared pillars/objectives. Flags drift and misalignment.
Also in 3 projects that use this
Dokkabei97Skillbrand-voice
Defines and enforces brand voice guidelines for startups. Creates tone, style, messaging frameworks and provides consistency checks across all content. Ensures every piece of communication sounds like it comes from the same brand.
Also in 4 projects that use this
MetaSkillroadmap
Build, continue, inspect, or visualize a source-grounded mathematical roadmap and theorem DAG in an existing Autoform Markdown blueprint. Use for source research, repository-wide inventories of existing and planned mathematics, scope, coverage, milestones, and roadmap articles; do not create repository infrastructure or prove Lean declarations.
Also in 3 projects that use this
AnthropicSkillbrief
Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.
Also in 4 projects that use this
AWSSkillretro
Conduct a retrospective on a coding session.
Also in 3 projects that use this
OpenAISkillaudit
Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.
Also in 3 projects that use this
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

