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.
What this skill does
# 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](references/x-posts.md) |
| X Threads | [x-threads.md](references/x-threads.md) |
| X Content Strategy | [x-strategy.md](references/x-strategy.md) |
| Hook Patterns | [hooks.md](references/hooks.md) |
| LinkedIn | [linkedin.md](references/linkedin.md) |
| Threads & Instagram | [threads-instagram.md](references/threads-instagram.md) |
| Facebook | [facebook.md](references/facebook.md) |
| AI Writing Avoidance | [ai-avoidance.md](references/ai-avoidance.md) |
| Style Guide | [style-guide.md](references/style-guide.md) |
| Technical Blog Styles | [technical-styles.md](references/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 |
| **LinkedIn** | 3,000 chars | 1,300 | 3-5 | Hook before "see more" |
| **Threads** | 500 chars | 400-500 | None | Conversational, no hashtags |
| **Instagram** | 2,200 chars | Varies | 5-15 | Visual-first, line breaks |
| **Facebook** | 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:
1. Read platform-specific guide
2. Read [ai-avoidance.md](references/ai-avoidance.md) — critical for human voice
3. Read [style-guide.md](references/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](references/ai-avoidance.md) — Most important, read first
- [hooks.md](references/hooks.md) — Hook patterns with examples
- [x-strategy.md](references/x-strategy.md) — What to share
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.