social-writer▌
itechmeat/llm-code · updated Apr 12, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Create platform-optimized social media content that sounds human, drives engagement, and builds audience.
Social Writer
Create platform-optimized social media content that sounds human, drives engagement, and builds audience.
Quick Navigation
| 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 Quick Reference
| 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 |
Content Type Router
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)
Writing Workflow
1. Select Platform & Format
Choose based on:
- Audience: Where do they spend time?
- Content depth: Quick insight vs deep dive
- Goal: Engagement, education, announcement
2. Load Style Reference
Before writing:
- Read platform-specific guide
- Read ai-avoidance.md — critical for human voice
- Read style-guide.md for tone
3. Draft Content
Apply platform constraints from start. Style informs structure.
4. Quality Check
Run through checklist below before posting.
Universal Quality Checklist
Voice
- Sounds like a person, not AI?
- Zero banned words (delve, unleash, harness, leverage)?
- Zero em-dashes (—)?
- Contractions used naturally?
Specificity
- Includes names, numbers, tools, dates?
- Concrete examples, not hypotheticals?
- Would I bookmark this if someone else wrote?
Structure
- Hook in first line?
- Sentence lengths vary (5-40 words)?
- Each paragraph/tweet can stand alone?
Value
- Teaches something specific?
- Actionable today?
- From real experience?
X Quick Start
Single Post Pattern
[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.
Thread Pattern
1/N [Bold hook - main insight] 👇
2/N [Context or setup]
3-N/N [Key points, one per tweet]
N/N [Summary + CTA]
Rules:
- First tweet MUST end with 👇 or 🧵 to signal thread
- Use N/M numbering (1/7, 2/7... 7/7)
- Each tweet must stand alone
- Max 5-7 tweets (longer = blog post)
High-Engagement Content Patterns
| 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 |
Content Selection: What to Share
Always Share ✓
- Shipped work + learnings
- Non-obvious insights
- Tool recommendations with specifics
- Solutions to common problems
Skip ✗
- Generic progress updates
- Plans before execution
- Obvious observations
- Engagement bait ("RT if you agree")
- Vague hype
Critical Prohibitions
- Do not use words: delve, unleash, harness, leverage, robust, seamless, game-changer, unlock
- Do not use em-dashes (—) anywhere
- Do not use "It's not X, it's Y" pattern
- Do not ask for engagement ("RT if you agree", "What do you think?")
- Do not use formal transitions (Furthermore, Moreover, Additionally)
- Do not write uniform sentence lengths
- Do not skip the hook
Links
- ai-avoidance.md — Most important, read first
- hooks.md — Hook patterns with examples
- x-strategy.md — What to share
How to use social-writer on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add social-writer
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches social-writer from GitHub repository itechmeat/llm-code and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate social-writer. Access the skill through slash commands (e.g., /social-writer) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ 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.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★45 reviews- ★★★★★Layla Bansal· Dec 28, 2024
Keeps context tight: social-writer is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Kofi Okafor· Nov 19, 2024
Useful defaults in social-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Neel Menon· Nov 19, 2024
I recommend social-writer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Liam Kapoor· Oct 10, 2024
social-writer has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Aarav Dixit· Oct 10, 2024
social-writer reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Neel Mehta· Sep 17, 2024
social-writer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Kofi Wang· Sep 17, 2024
social-writer reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Emma Yang· Sep 17, 2024
Solid pick for teams standardizing on skills: social-writer is focused, and the summary matches what you get after install.
- ★★★★★Lucas Martin· Sep 13, 2024
social-writer has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Rahul Santra· Sep 5, 2024
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