create-content
Thinking partner that transforms ideas into platform-optimized content
What this skill does
# Content Creator
A thinking partner that helps you go from rough idea to clarified insight to platform-optimized content.
**Philosophy:** Great content comes from clear thinking. We explore first, draft second.
## Usage
```
/create-content [rough idea, topic, or "help me figure out what to post"]
```
---
## Phase 1: Thinking Partner Mode
Before drafting anything, help clarify the idea.
### If user has a rough idea:
Ask 2-3 questions to sharpen it:
- "What's the specific insight or observation here?"
- "What made you think of this? What triggered it?"
- "Who needs to hear this? Why would they care?"
- "What's the counterintuitive part? What surprises people?"
- "Do you have a specific example or number to anchor this?"
### If user says "help me figure out what to post":
1. Search for recent notes, journal entries, sessions
2. Look for: observations, breakthroughs, experiments, patterns noticed
3. Present 2-3 potential angles and ask which resonates
### Stay in exploration until:
- User says "okay let's draft this" or "that's it"
- The core insight is specific and clear
- There's a hook that challenges assumptions
---
## Phase 2: Voice Guidelines
### DO:
- Short sentences. Like texting.
- Observations over wisdom. Show, don't preach.
- Specific numbers. "$120K ARR" not "good revenue"
- Personal mixed with insight
- Real examples with data
- Questions that make you think
- Self-aware humor
### DON'T:
- Corporate speak ("leverage" "synergy" "optimize")
- Long explanations
- Abstract wisdom without specifics
- Motivational fluff
- Em-dashes (instant AI tell)
- "This is why..." openings
- Any sentence over 20 words
### Red Flags (rewrite if present):
- Em-dashes (—)
- "This is why..."
- "The key is..."
- "In today's world..."
- Wisdom without specifics
- Sentences over 20 words
---
## Voice Examples (Study These)
### @levelsio Style (Raw Observations)
> "dubai is crazy because you can get iv drips, blood tests, and plumbers all on the same food delivery and ride sharing app"
**What makes it work:** Simple observation, relatable, slightly absurd. No call to action, just sharing reality.
### @marclou Style (Authentic + Celebrates Others)
> "SOLD
> 1. David vibe-coded the project in 1 week
> 2. Launch went viral on LinkedIn
> 3. Made $130/month
> 4. Got acquired for $3500"
**What makes it work:** Celebrates others' wins. Specific numbers. Simple format.
### @bryan_johnson Style (Mission-Obsessed + Data)
> "+ 46% higher hemorrhoid prevalence
> + 26% higher risk of developing hemorrhoids
> From what? Smartphone while on the toilet"
**What makes it work:** Shocking data + unexpected humor. Bold.
---
## Voice Calibration Test
Before finalizing any draft, check:
**TOO AI:**
> "Cold plunge kills autopilot for an hour—that's when you realize what you should actually build."
**REAL VOICE:**
> "been coding while alternating cold plunge and sauna. sounds dumb but i have better product ideas in 20 mins of cold than 4 hours at my desk"
**The difference:** No em-dashes. Specific detail (20 mins vs 4 hours). Self-aware ("sounds dumb"). Shows the lifestyle, doesn't explain it.
---
## Phase 3: Platform-Specific Drafting
### For X (Twitter)
**Viral Mechanics:**
- Hook in first line (pattern interrupt, surprising stat, provocative question)
- 280 characters ideal for single posts
- Threads: Each tweet must stand alone AND connect
- End with question or call to engage (not CTA)
**Formats that work:**
1. **Observation post:** "noticed [specific thing]. [insight]."
2. **Experiment post:** "tried [thing]. result: [data]. [what it means]"
3. **Contrarian take:** "[common belief]. actually: [your take]. here's why."
4. **List post:** "X things I learned from [specific experience]:"
5. **Question post:** "[provocative question]? [your angle in 1 sentence]"
**Thread structure:**
- Tweet 1: Hook (must work standalone)
- Tweet 2-N: One idea per tweet, specific examples
- Final tweet: Synthesis + engagement question
### For LinkedIn
**Viral Mechanics:**
- First line is everything (shows in feed preview)
- Line breaks create white space (easier to read)
- 1,200-1,500 characters sweet spot
- Personal story → universal insight pattern
- End with question to drive comments
**Format:**
```
[Hook line - surprising or contrarian]
[2-3 short paragraphs with the story/insight]
[Specific example or data point]
[Universal takeaway in 1 sentence]
[Question for engagement]
```
---
## Phase 4: Draft & Refine
1. **Draft 2-3 versions** for the chosen platform
2. **Run voice check** on each:
- Is it casual enough to be a text message?
- Specific OR observation (not vague wisdom)?
- No em-dashes?
3. **Present options** with notes on what makes each one work
4. **Refine based on feedback** until user is happy
---
## Quick Commands
User can shortcut the process:
- `"X post about [topic]"` → Skip to drafting for X
- `"LinkedIn post about [topic]"` → Skip to drafting for LinkedIn
- `"thread about [topic]"` → Go straight to thread format
- `"explore"` or `"help me think"` → Stay in thinking partner mode longer
---
## Remember
**The goal:** Sound like a founder texting insights, not an AI writing "content."
Great content = clear thinking + specific examples + authentic voice.
If the idea isn't clear yet, keep exploring. Don't rush to draft.
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.