ideation

A tool for generating YouTube video ideas from existing research and competitive analysis. It identifies possible angles, audience desires, and gaps between competing videos.

In plain words
What is it for?
Use it to brainstorm videos, find angles on a topic, plan a next upload, or prepare idea briefs for hooks and full outlines.
Why use it?
It helps turn research into specific content directions without repeating a full research process. It also makes it easier to choose an angle that differs from similar videos.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/ai-answer/contentrepurposesystem/ideation
Any agent
npx skills add AI-Answer/ContentRepurposeSystem --skill ideation
Clone the repo
git clone --depth 1 https://github.com/AI-Answer/ContentRepurposeSystem

Made for: Claude Code, Codex.

Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,812 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00091 $0.01812
Opus 5 $0.00046 $0.00906
Sonnet 5 $0.00018 $0.00362
Haiku 4.5 $0.00009 $0.00181

Measured 2d ago against content hash c1df39b47a5e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ideation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/ideation/SKILL.md · 172 lines

How it starts

The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Video Ideation Engine

Generate positioned YouTube video ideas grounded in existing research and competitive analysis. Outputs structured idea briefs ready to feed into /hooks and /outlines.

This skill is strategy, not research. It consumes research outputs from /yt-pipeline, /firecrawl-search, or vault notes. It does NOT replicate deep research — if no research exists yet, it runs a lightweight competitive scan only.

When This Skill Activates

Activate when the user wants to:

  • Brainstorm video ideas on a topic
  • Figure out what video to make next
  • Find angles on a trending topic
  • Generate content ideas from research they've already done

Example triggers:

  • "Give me video ideas about RAG"
  • "What should I make a video about this week?"
  • "Brainstorm some Claude Code video angles"
  • /ideation or /ideation <topic>

Workflow

Step 1 — Gather Existing Context

Check what research already exists before doing anything:

  1. Search the vault — look in research/ and projects/ for files related to the topic
  2. Check for recent yt-pipeline or firecrawl-search outputs — these are your primary source material
  3. If the user references specific notes, read them

If research exists: Use it as the foundation. Do NOT re-research the topic.

If no research exists: Do a lightweight competitive scan only (Step 2). Suggest the user run /yt-pipeline <topic> or /firecrawl-search <topic> first if they want deeper analysis.

Step 2 — Lightweight Competitive Scan

Quick YouTube search to see what exists — this is positioning intel, not deep research:

Optional step. This uses a separate yt-search helper script that does not ship with this plugin. If it isn't installed, skip the scan and generate ideas from the user's described topic and any vault/research context instead — the rest of the skill works fine without it.

python "${CLAUDE_PLUGIN_ROOT}/skills/yt-search/scripts/search.py" <topic keywords> --count 15 --months 3

Read the full file on GitHub · 172 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 172 lines · 91 tokens per session scan A c1df39b47a5e

Subscribe to this mod's changes

ideation is a skill published in the GitHub repository AI-Answer/ContentRepurposeSystem (12 stars, last pushed 2mo ago), licensed MIT. It adds 91 tokens to every session and 1,812 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

feature-state-keeper

Use when starting, advancing, finishing, or blocking a feature. Manages featurelist.json + progress.md + session-handoff.md. Default-FAIL enforced.

Redtropig/harness-anchor · 37 tokens

anti-hallucination-gates

Use before claiming done/fixed/passing — or before asserting something is absent: not installed, not available, no such function, couldn't find it. Default-FAIL runs both ways — every claim needs an evidence path. A negative claim must carry its search scope and observation date; state calibrated uncertainty when…

Redtropig/harness-anchor · 72 tokens

cpp-static-analysis

Use in C/C++ projects when reviewing changes or hunting bugs. Runs clang-tidy/cppcheck/IWYU. Needs compilecommands.json. Changed lines only.

Redtropig/harness-anchor · 37 tokens

capturing-golden-rules

Use when the same mistake or bad pattern recurs, when a code-review comment is really a convention worth enforcing, or when you catch AI-generated drift/slop and want it to never happen again. Encodes the lesson as a durable rule in golden-rules.md — the feedback-flywheel / harness-layer-learning ratchet — instead of…

Redtropig/harness-anchor · 87 tokens

cpp-sanitizers

Use in C/C++ projects for crashes, hangs, UB, data races, memory errors. ASan/UBSan/TSan runtime checks. Build sanitizer config separately.

Redtropig/harness-anchor · 40 tokens

docs-lookup

Use when looking up unfamiliar tools, APIs, errors, library behavior. Context7 → WebSearch → calibrated uncertainty fallback chain. Don't guess.

Redtropig/harness-anchor · 32 tokens