content-idea-generator
Generate content ideas rooted in positioning. Use when someone needs "content ideas," "what should I post," "blog topics," "LinkedIn ideas," or is stuck on what to create.
What this skill does
# Content Idea Generator
Content without positioning is noise. Before generating ideas, confirm positioning is clear. If not, run `positioning-basics` first.
---
## Mode
Detect from context or ask: *"Quick ideas, full strategy, or complete content system?"*
| Mode | What you get | Best for |
|------|-------------|----------|
| `quick` | 5 ideas, immediate output, no deep research | Breaking a block, starter brainstorm |
| `standard` | 10–15 positioned ideas with formats and rationale | Regular content planning |
| `deep` | Full content calendar system: pillars, formats, cadence, 30-day plan | Launching or overhauling content strategy |
**Default: `standard`** — use `quick` if they just need to start. Use `deep` if they want a repeatable system, not just today's ideas.
---
## Context Loading Gates
**Before generating any ideas, collect:**
- [ ] **Positioning statement:** "I help [specific audience] with [specific outcome] through [unique approach]." Must be specific — not "I help businesses grow."
- [ ] **ICP specifics:** What are the top 3 frustrations or questions the ideal customer has right now?
- [ ] **Recent wins or proof points:** Any client results, experiments, or lessons from the last 30 days?
- [ ] **Content formats available:** LinkedIn? Twitter/X? Newsletter? Short video? All?
- [ ] **Prior content strategy:** Any existing pillars from `linkedin-authority-builder`? Don't generate outside those pillars if they exist.
**Positioning gate:** If the user cannot complete the positioning sentence with specifics, stop:
> "Content without positioning produces random posts. Complete this first: 'I help [specific audience] achieve [specific outcome] through [unique approach].' If you need help, run `positioning-basics` first."
---
## Phase 1: Context Analysis
Before generating ideas, reason through:
1. **Positioning strength:** Is the one-liner specific enough to anchor content ideas? A vague positioning produces vague ideas.
2. **Proof point audit:** What real results, experiments, or opinions does the user have? Generic ideas come from generic inputs — specific proof points produce specific content.
3. **Platform match:** Different platforms need different idea formats. LinkedIn rewards frameworks and stories; Twitter rewards brevity and contrarian takes; newsletters reward depth and curation.
4. **Content gap:** What has the user NOT covered yet that their ICP is actively asking about?
Output a brief analysis:
> "You're creating content for [audience] as a [role]. Your strongest proof point is [X]. I'll generate ideas anchored to that — the biggest content gap I see is [specific gap]."
---
## Phase 2: Freshness Check (Tool Call)
Run a search before generating the batch:
```
web_search('[Topic] trending [Month Year]')
web_search('[ICP role] biggest challenges [Year]')
```
Use results to:
- Identify timely angles on evergreen topics
- Spot what competitors aren't covering (your opportunity)
- Include at least 1 current-moment hook in the batch
---
## Phase 3: Idea Generation with Quality Filter
Generate ideas using these 6 frameworks:
### 1. The Problem Call-Out
Name the pain your audience won't admit publicly.
**Template:** "The #1 mistake [audience] makes with [topic]"
### 2. The "Here's What Works" Breakdown
Teach a specific process you've actually used.
**Template:** "How to [achieve outcome] without [common obstacle]"
### 3. The Contrarian Take
Challenge something everyone assumes is true.
**Template:** "Stop [common advice]. Here's what actually works."
### 4. The Behind-the-Curtain Story
Show the messy reality, not the highlight reel.
**Template:** "I [tried thing]. Here's what actually happened."
### 5. The Pattern Recognition
Connect dots your audience hasn't connected yet.
**Template:** "What [experience A] taught me about [topic B]"
### 6. The Resource Stack
Curate genuinely useful tools.
**Template:** "[Number] tools I actually use for [outcome]"
---
## Phase 4: Quality Filter (Run Every Idea Through This)
Each idea must pass all 3 tests before being included in the output:
1. **Specific?** — Does it have a concrete angle? ("How to use LinkedIn" → fails. "How to get DMs from framework posts with <500 followers" → passes.)
2. **Has a hook angle?** — Can you write a specific first line that stops the scroll?
3. **Connects to ICP pain?** — Does it address a real, named frustration of the target customer?
Reject and replace any idea that fails 2 or more tests.
---
## Phase 5: Self-Critique Pass (REQUIRED)
After generating the full batch, evaluate:
- [ ] Are all ideas anchored to the stated positioning, or did any drift outside the lane?
- [ ] Does each idea have a specific enough hook that I could write the first line right now?
- [ ] Are the Quick Wins genuinely low-effort to produce, or are they actually complex pieces?
- [ ] Is at least one idea tied to a real proof point or story the user mentioned?
- [ ] Did the freshness search produce anything useful, or were results too generic?
Flag and replace any ideas that don't pass: "Idea 3 ('thoughts on AI in marketing') is too broad for your positioning as a [specific role]. Replaced with: [specific angle]."
---
## Fluff Filter: Do Not Include
❌ "Grateful for the journey" posts — show the work instead
❌ Generic motivational quotes without a specific take
❌ Vague "thought leadership" with no actual opinion
❌ Engagement bait with no value ("Agree? Comment below")
❌ Topics outside the stated positioning
**The test:** Would you stop scrolling and read this if someone else posted it?
---
## Output Structure
```markdown
## Content Ideas: [Name] — [Date]
**Positioning used:** [one-liner]
**Freshness search:** [query + key finding]
---
### Quick Wins (Post This Week)
*5 ideas ready to create now*
**1. [Title/Angle]**
- Hook: "[First line that stops the scroll]"
- Core insight: [The one thing they'll remember]
- Platform fit: [LinkedIn / Twitter / Newsletter]
- ICP pain: [What frustration this addresses]
- Quality check: [Specific ✅ | Hook ✅ | ICP ✅]
[Repeat for ideas 2–5]
---
### Authority Builders (This Month)
*3 ideas worth the investment*
**1. [Title/Angle]**
- Hook: "[First line]"
- Core insight: [Key takeaway]
- Platform fit: [Platform]
- Research needed: [What to find first]
- Estimated production time: [X hours]
[Repeat for ideas 2–3]
---
### Self-Critique Notes
[Any ideas replaced, gaps noted, or freshness findings]
### Multi-Agent Handoff
For each approved idea → pass to Scribe with format:
[Idea title] | [Platform] | [Hook] | [Framework type] | [ICP pain addressed]
```
---
*Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com*
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.