Create platform-optimized social media content that sounds human, drives engagement, and builds audience.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsocial-writerExecute the skills CLI command in your project's root directory to begin installation:
Fetches social-writer from itechmeat/llm-code and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate social-writer. Access via /social-writer in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
12
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
12
stars
Create platform-optimized social media content that sounds human, drives engagement, and builds audience.
| Topic | Reference |
|---|---|
| X Single Posts | x-posts.md |
| X Threads | x-threads.md |
| X Content Strategy | x-strategy.md |
| Hook Patterns | hooks.md |
| linkedin.md | |
| Threads & Instagram | threads-instagram.md |
| facebook.md | |
| AI Writing Avoidance | ai-avoidance.md |
| Style Guide | style-guide.md |
| Technical Blog Styles | technical-styles.md |
| Platform | Limit | Best Length | Hashtags | Key Rule |
|---|---|---|---|---|
| X | 280 chars | 230-280 | 1-2 max | Hook in first line, use full space |
| 3,000 chars | 1,300 | 3-5 | Hook before "see more" | |
| Threads | 500 chars | 400-500 | None | Conversational, no hashtags |
| 2,200 chars | Varies | 5-15 | Visual-first, line breaks | |
| Unlimited | <250 | 2-3 | Community, engagement |
What are you creating?
│
├─ X?
│ ├─ Single insight/observation → x-posts.md
│ ├─ Multi-part story/tutorial → x-threads.md
│ └─ Content planning → x-strategy.md
│
├─ LinkedIn → linkedin.md
│ └─ Professional, B2B, thought leadership
│
├─ Threads/Instagram → threads-instagram.md
│ └─ Conversational, authentic, visual
│
├─ Facebook → facebook.md
│ └─ Community, engagement, events
│
└─ Technical blog → technical-styles.md
├─ Karpathy style (conversational, personal)
└─ Deep technical (opinion-forward, contrarian)
Choose based on:
Before writing:
Apply platform constraints from start. Style informs structure.
Run through checklist below before posting.
[Hook - stop the scroll]
[Context or specific detail]
[Insight or learning]
[Optional: engagement question]
Example:
Shipped curation v1 for agents.foo today.
Discovery is way harder than app stores. Agents are conversations, not static features.
Had to rebuild around context matching instead of keyword search.
1/N [Bold hook - main insight] 👇
2/N [Context or setup]
3-N/N [Key points, one per tweet]
N/N [Summary + CTA]
Rules:
| Pattern | Structure | Best For |
|---|---|---|
| Shipped X, Learned Y | What shipped + key learning + why it matters | Project updates |
| How to X | Problem + steps + key insight | Tutorials |
| Problem → Solution | Problem + failed attempts + what worked | Case studies |
| Contrarian | Popular belief + why wrong + your evidence | Thought leadership |
| Tool Recommendation | Tool + specific benefit + real example | Resources |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
jezweb/claude-skills
Keeps context tight: social-writer is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in social-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend social-writer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
social-writer has been reliable in day-to-day use. Documentation quality is above average for community skills.
social-writer reduced setup friction for our internal harness; good balance of opinion and flexibility.
social-writer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
social-writer reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: social-writer is focused, and the summary matches what you get after install.
social-writer has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: social-writer is focused, and the summary matches what you get after install.
showing 1-10 of 45