跳到正文
cccskills
免费在 GitHub 公开

talk-pipeline

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.

查看安装方法

适用场景

  • Prepare a talk from articles or notes
  • Build an experience report supported by Git history
  • Develop a script after choosing an angle and title
  • Rerun a single preparation stage

包含的文件(1)

  • SKILL.md5.7 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Talk pipeline orchestrator

Orchestrates the complete talk preparation pipeline from raw material to revision sheets. Can run the full pipeline or a single isolated stage.

Modes

  • --rex: REX talk with git/code proof (changelog, commits, measured metrics)
  • --concept: Conceptual talk from article, ideas, notes (skips Stage 2)

Usage

/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

Context collection

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

Workflow

  1. Collect context using AskUserQuestion for required metadata
  2. Route by mode (--rex vs --concept, skip Stage 2 if concept)
  3. Run Stage 1 (/talk-stage1-extract, always first)
  4. Run Stages 2-4 in parallel (after Stage 1 confirmed)
    • REX: extract -> research + concepts + position (in parallel)
    • Concept: extract -> concepts + position (in parallel, skip research)
  5. CHECKPOINT: wait for angle + title choice (Stage 4 output)
  6. Run Stage 5 (/talk-stage5-script with validated choice)
  7. Run Stage 6 (/talk-stage6-revision)
  8. Final summary: list all generated files with their paths

Dependency graph

         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)

Stage Routing (--stage=X)

If --stage is provided, run only the corresponding skill:

StageSkill 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

Output naming convention

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

Final summary format

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.

Anti-patterns

  • Do not run Stage 5 without an explicit angle + title choice from the user
  • Do not run Stage 2 (research) in --concept mode
  • Do not proceed to the next stage if an upstream stage failed
  • Do not invent metrics or dates not present in the source material

Validation

  • All upstream files exist before launching a downstream stage
  • Stage 4 CHECKPOINT respected before script
  • Outputs named per convention talks/{YYYY}-{slug}-{stage}.md
  • No empty placeholders in generated files

Tips

  • The orchestrator is the recommended entry point for first use
  • For repeat users who know the pipeline, running individual stage skills is faster
  • The --stage=X flag is useful for rerunning a single stage without redoing the full pipeline

Related

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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.

中文简介正在准备中。当前显示英语简介。

  • Review skills before release
  • Compare agent definitions with reference templates
  • Quickly check critical quality criteria
FlorianBruniaux/claude-code-ultimate-guide62112026年10月20日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Assessing the overall health of an inherited project
  • Reviewing exposed credentials and security risks
  • Identifying dependency and test coverage gaps
FlorianBruniaux/claude-code-ultimate-guide62112026年10月20日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Finding code patterns to prioritize for cleanup
  • Preparing measurement files for an improvement loop
  • Repeating targeted edits to reduce casts to any
FlorianBruniaux/claude-code-ultimate-guide62112026年10月20日 更新

best-of-n

免费

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.

中文简介正在准备中。当前显示英语简介。

  • Comparing implementation options before choosing one
  • Verifying a solution when a wrong choice would be costly
  • Keeping evaluation evidence for delivery or audit
FlorianBruniaux/claude-code-ultimate-guide62112026年10月20日 更新

canary

免费

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.

中文简介正在准备中。当前显示英语简介。

  • Recording a healthy baseline before deployment
  • Monitoring production immediately after deployment
  • Checking key pages for slower responses or failures
FlorianBruniaux/claude-code-ultimate-guide62112026年10月20日 更新

catchup

免费

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.

中文简介正在准备中。当前显示英语简介。

  • Restoring project context after /clear
  • Reviewing recent changes after a long break
  • Checking unfinished work before choosing the next task
FlorianBruniaux/claude-code-ultimate-guide62112026年10月20日 更新

查看 FlorianBruniaux 的全部技能

报告此技能的问题