メニュー
Use when you've delivered a talk and want to convert it into blog posts, social content, newsletter sections, and republishing pitches — or when you have presentation materials (slides, transcript, speaker notes) that could reach wider audiences. Produces multiple content pieces from a single talk.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when you have a single piece of content (blog post, talk, case study, docs PR) and want to extract multiple content angles from it — abstraction ladders, audience pivots, controversy checks, and hidden assumptions that could each become their own piece.
Use when you want to discover content series across your existing work — finds clusters by theme rather than topic, identifies repeated points from different angles, flags incomplete arcs, and suggests series framing that makes relationships explicit.
Use when you've solved a user problem, answered a support question, or helped someone with a technical issue and want to turn it into shareable content. Produces both short-form "TIL" and long-form fully-contextualized pieces, plus recommends the right format (docs, blog, talk).
Turn a CFP submission into a structured talk outline with section timings, theory/practical balance, demo risk assessments, fallback plans, and Patrick Winston opening/close principles applied throughout.
Generate a speaker or author bio through a short Q&A. Controls for length, person (first or third), and a slider for how much to centre the current employer vs. broader career and personal brand.
Generate a complete conference proposal through a structured brainstorming Q&A. Produces abstract, extended abstract, title variants, and learning outcomes — calibrated to the session format and grounded in your DevRel context.
| name | repurpose-talk |
| description | Use when you've delivered a talk and want to convert it into blog posts, social content, newsletter sections, and republishing pitches — or when you have presentation materials (slides, transcript, speaker notes) that could reach wider audiences. Produces multiple content pieces from a single talk. |
Before doing anything else:
~/.devadvokit.md exists.This skill produces outlines, angles, and frameworks — not full drafts. Specifically:
The goal is multiple content directions from one talk, not finished pieces. Editing produces the final versions.
Ask these questions one at a time. Wait for each answer before asking the next.
What's the talk title and abstract? (Paste or type — this is required. If you only have a title and need help with an abstract, say so and I'll help you draft one.)
Do you have a script, speaker notes, or transcript? Paste it here or provide a file path. This allows me to ground outputs in your actual content rather than infering from the abstract alone. If you only have the abstract, I can still work with that.
Who's the target audience for the repurposed content, and what's their familiarity level? (Beginner / practitioner / expert — this affects depth and terminology)
What tone should the repurposed content have? (Technical and depth-focused? Conversational and approachable? Thought leadership and industry perspective?)
What conference or event was this presented at, and when? (This gives context and provides "as I presented at X" framing for the repurposed content)
If transcript or notes were provided, process them before generating outputs:
Pull 2–3 pull quotes — direct lines that work as standalone social copy. Memorable, quotable, out-of-context friendly.
Flag demo or live content — anything that won't translate to written formats. Note what needs adaptation or removal.
Note claims needing sources — assertions, data points, or claims requiring a source link before publishing.
If only the abstract was provided, skip this section and work from what you have.
Produce all of the following once the Q&A is complete and quality gates (if applicable) have been processed.
H2 structure with per-section notes (not the full draft). Each section has a brief note on what it covers and the key point it makes. Grounded in the actual talk content if transcript/notes were provided.
Each with a different hook strategy:
Each angle should be distinct in tone and approach. Include a brief note on why this angle works for this content.
Opening tweet only, with a brief note on thread direction. Each starter should lead in a different way — anecdote, provocative statement, practical tip, etc.
150–200 words, designed to slot into an existing newsletter. Includes a hook, key insight from the talk, and a link/call to action. Written in newsletter voice (conversational, direct).
One paragraph (4–6 sentences) for republishing on a third-party publication. Includes the pitch angle, why it fits that publication's audience, and a brief credibility anchor. Grounded in the conference context ("As presented at X...").
Scan the content library in ~/.devadvokit.md. If any existing content covers similar ground:
"This overlaps with [title] ([year]) — consider cross-linking or positioning as an update / deeper dive."
If nothing overlaps, omit this section entirely.
Before presenting any output, read ../../shared/ai-antipatterns.md and silently rewrite any flagged patterns. Do not mention this step to the user.