Turn articles, notes, or code history into talk preparation materials, including angles, titles, scripts, slide drafts, and revision sheets. Coordinate the stages with user checkpoints, or run an individual stage again.
Orchestrates the complete talk preparation pipeline from raw material to revision sheets, running 6 stages in sequence with human-in-the-loop checkpoints for REX or Concept mode talks. Use when starting a new talk pipeline, resuming a pipeline from a specific stage, or running the full end-to-end preparation workflow.
Review the instructions the agent will receive before you install.
Orchestrates the complete talk preparation pipeline from raw material to revision sheets. Can run the full pipeline or a single isolated stage.
--rex: REX talk with git/code proof (changelog, commits, measured metrics)--concept: Conceptual talk from article, ideas, notes (skips Stage 2)/talk-pipeline # full pipeline, asks for context
/talk-pipeline --stage=extract # run a single isolated stage
/talk-pipeline --rex # REX mode (git archaeology included)
/talk-pipeline --concept # Concept mode (skip research)
/talk-pipeline --rex --slug=my-talk --event="Conf 2026" --date=2026-06-15 --duration=30
Ask with AskUserQuestion if not provided:
- slug : kebab-case identifier (e.g., my-talk-topic)
- event : event name (e.g., Conf 2026, Tech Meetup)
- date : talk date (YYYY-MM-DD)
- duration : duration in minutes (e.g., 30)
- audience : audience profile (e.g., senior devs, tech leads, non-tech)
- type : --rex or --concept
- source_path : path to source material (article .mdx, transcript .md, notes)
- repo_path : (REX only) path to git repository for archaeology
--rex vs --concept, skip Stage 2 if concept)/talk-stage1-extract, always first)/talk-stage5-script with validated choice)/talk-stage6-revision) extract (Stage 1)
|
+----------+-----------+
v v v
research concepts position
(Stage 2) (Stage 3) (Stage 4)
[--rex only] [CHECKPOINT]
| | |
+----------+-----------+
v
script (Stage 5)
|
v
revision (Stage 6)
If --stage is provided, run only the corresponding skill:
| Stage | Skill to invoke |
|---|---|
| extract | /talk-stage1-extract |
| research | /talk-stage2-research |
| concepts | /talk-stage3-concepts |
| position | /talk-stage4-position |
| script | /talk-stage5-script |
| revision | /talk-stage6-revision |
talks/{YYYY}-{slug}-summary.md # extract
talks/{YYYY}-{slug}-git-archaeology.md # research
talks/{YYYY}-{slug}-changelog-analysis.md
talks/{YYYY}-{slug}-timeline.md
talks/{YYYY}-{slug}-concepts.md # concepts
talks/{YYYY}-{slug}-concepts-enriched.md
talks/{YYYY}-{slug}-angles.md # position
talks/{YYYY}-{slug}-titre.md
talks/{YYYY}-{slug}-descriptions.md
talks/{YYYY}-{slug}-feedback-draft.md
talks/{YYYY}-{slug}-pitch.md # script
talks/{YYYY}-{slug}-slides.md
talks/{YYYY}-{slug}-kimi-prompt.md
talks/{YYYY}-{slug}-revision-sheets.md # revision
After Stage 6 completes, display:
Pipeline complete. Files generated:
Stage 1: Extract
v talks/{YYYY}-{slug}-summary.md
Stage 2: Research (REX only)
v talks/{YYYY}-{slug}-git-archaeology.md
v talks/{YYYY}-{slug}-changelog-analysis.md
v talks/{YYYY}-{slug}-timeline.md
Stage 3: Concepts
v talks/{YYYY}-{slug}-concepts.md
v talks/{YYYY}-{slug}-concepts-enriched.md (if repo available)
Stage 4: Position
v talks/{YYYY}-{slug}-angles.md
v talks/{YYYY}-{slug}-titre.md
v talks/{YYYY}-{slug}-descriptions.md
v talks/{YYYY}-{slug}-feedback-draft.md
Stage 5: Script
v talks/{YYYY}-{slug}-pitch.md
v talks/{YYYY}-{slug}-slides.md
v talks/{YYYY}-{slug}-kimi-prompt.md <- copy-paste into kimi.com
Stage 6: Revision
v talks/{YYYY}-{slug}-revision-sheets.md
Next step: open kimi-prompt.md, verify no {PLACEHOLDER} remains, paste into kimi.com.
--concept modetalks/{YYYY}-{slug}-{stage}.md--stage=X flag is useful for rerunning a single stage without redoing the full pipelineNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Evaluate Claude Code agents, skills, and commands with weighted quality criteria. Get scores, readiness grades, template comparisons, and practical improvement suggestions in Markdown or JSON reports to guide reviews before release.
Assess a codebase across seven areas, including exposed credentials, security, dependencies, structure, and tests. Receive category scores, findings tied to file locations, and a prioritized improvement plan with smaller tasks that can be completed quickly.
Measure code patterns such as casts to any or disabled lint rules, then run repeated, targeted edits. Keep changes that improve the chosen metric, revert unsuccessful changes, and track results for each improvement loop.
Generate several separate solutions, compare them against criteria fixed in advance, and verify the selected result through executable checks or an independent reviewer. Keep a proof log documenting candidates, evidence, failures, and remaining limits.
Monitor a live application after deployment and compare it with a saved baseline, a record of its earlier state. Check page responses, loading times, and new errors, flag persistent changes, and produce a per-page health report.
Rebuild project context after clearing a conversation or returning to work. Review recent Git history, uncommitted changes, and TODO markers to get a structured summary of project status and suggested next steps.