social-writer

Create engaging content for social media platforms: X posts and threads, LinkedIn, Threads, Instagram, Facebook. Includes writing styles, AI-avoidance patterns, hooks catalog, and macOS Notes integration. Use when drafting social media posts, writing thread series, applying engagement hooks, or adapting content for specific platforms. Keywords: social media, X, LinkedIn, threads, posts, hooks, content strategy, AI writing avoidance.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "social-writer" with this command: npx skills add itechmeat/llm-code/itechmeat-llm-code-social-writer

Social Writer

Create platform-optimized social media content that sounds human, drives engagement, and builds audience.

Quick Navigation

TopicReference
X Single Postsx-posts.md
X Threadsx-threads.md
X Content Strategyx-strategy.md
Hook Patternshooks.md
LinkedInlinkedin.md
Threads & Instagramthreads-instagram.md
Facebookfacebook.md
AI Writing Avoidanceai-avoidance.md
Style Guidestyle-guide.md
Technical Blog Stylestechnical-styles.md

Platform Quick Reference

PlatformLimitBest LengthHashtagsKey Rule
X280 chars230-2801-2 maxHook in first line, use full space
LinkedIn3,000 chars1,3003-5Hook before "see more"
Threads500 chars400-500NoneConversational, no hashtags
Instagram2,200 charsVaries5-15Visual-first, line breaks
FacebookUnlimited<2502-3Community, 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:

  1. Read platform-specific guide
  2. Read ai-avoidance.md — critical for human voice
  3. 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

PatternStructureBest For
Shipped X, Learned YWhat shipped + key learning + why it mattersProject updates
How to XProblem + steps + key insightTutorials
Problem → SolutionProblem + failed attempts + what workedCase studies
ContrarianPopular belief + why wrong + your evidenceThought leadership
Tool RecommendationTool + specific benefit + real exampleResources

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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

react-testing-library

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

mantine-dev

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

commits

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

skill-master

No summary provided by upstream source.

Repository SourceNeeds Review