find-content-angles

A content-planning skill that finds several possible angles from one source, such as a blog post, talk, case study, or documentation change.

In plain words
What is it for?
Use it to discover content directions and frameworks; it does not produce finished drafts, search keywords, or social posts.
Why use it?
It helps turn one finished piece into future topics by examining audiences, assumptions, abstractions, and possible controversies.

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/phazonoverload/devadvokit/find-content-angles
Any agent
npx skills add phazonoverload/devadvokit --skill find-content-angles
Clone the repo
git clone --depth 1 https://github.com/phazonoverload/devadvokit

Made for: Claude Code, Codex.

Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 902 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.00058 $0.00902
Opus 5 $0.00029 $0.00451
Sonnet 5 $0.00012 $0.00180
Haiku 4.5 $0.00006 $0.00090

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

Security

Grade A, and why

find-content-angles 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/find-content-angles/SKILL.md · 103 lines

How it starts

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

Before doing anything else:

  1. Check if ~/.devadvokit.md exists.
  2. If it does, read it silently and use it throughout this skill.
  3. If it does not, stop and tell the user: "I need your DevRel context before I can run this skill. Please run /setup-devadvokit first."

What NOT to Do

This skill produces angles, frameworks, and directions — not finished content. Specifically:

  • No full drafts — you're finding the seeds of future pieces, not writing them
  • No SEO keyword research — that's a different skill for a different workflow
  • No social media posts — use /repurpose-talk for that

The goal is content strategy discovery, not content production.


Q&A

Ask these questions one at a time. Wait for each answer before asking the next.

  1. What's the content piece? Paste or describe it — blog post, talk abstract, case study, docs PR, etc. This is your source material.

  2. What was the core insight or lesson here, in one sentence? (What's the one thing you want people to take away?)

  3. Who was the original audience for this piece? (The people you wrote it for the first time.)

  4. What response did this get when you published it? (Comments, questions, "but what about X" — these are clues for angles you didn't explore.)


Output

Produce all of the following once the Q&A is complete.

1. Abstraction Ladder

Start with the specific problem you solved, then climb up 3 levels of generalization:

  • Level 1 (specific): [What you actually did]
  • Level 2 (pattern): [What this is an instance of]
  • Level 3 (principle): [What principle this demonstrates]
  • Level 4 (universal): [What universal truth this points to]

Include one sentence on when each level is the right framing for a new piece.

2. Audience Pivots

The same insight reframed for different readers. Generate 3 pivots:

  • Pivot 1: [Different job role perspective]
  • Pivot 2: [Different experience level perspective]
  • Pivot 3: [Different context/industry perspective]

Read the full file on GitHub · 103 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 · 103 lines · 58 tokens per session scan A 443a3a2d738e

Subscribe to this mod's changes

find-content-angles is a skill published in the GitHub repository phazonoverload/devadvokit (16 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 902 once invoked, about $0.0003 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens