BD talk-pipeline
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.
Orchestrates the complete talk preparation pipeline from raw material to revision sheets, running 6 stages in sequence with human-in-the-loop checkpoints for…
As a process D 36/100 · Unfinished process — References files that are not bundled: ../stage-1-extract/SKILL.md, ../stage-2-research/SKILL.md, ../stage-3-concepts/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../stage-1-extract/SKILL.md - warning
missing-refreference to a missing file: ../stage-2-research/SKILL.md - warning
missing-refreference to a missing file: ../stage-3-concepts/SKILL.md - warning
missing-refreference to a missing file: ../stage-4-position/SKILL.md - warning
missing-refreference to a missing file: ../stage-5-script/SKILL.md - warning
missing-refreference to a missing file: ../stage-6-revision/SKILL.md - warning
missing-refreference to a missing file: ../../../../guide/workflows/talk-pipeline.md - note
frontmatter-keyunknown frontmatter key "effort"
Process rating: all ten parameters 36/100
- 0Tools and files. 7 referenced file(s) missing: ../stage-1-extract/SKILL.md, ../stage-2-research/SKILL.md, ../stage-3-concepts/SKILL.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (talk-pipeline) differs from the folder (orchestrator)
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 30 steps
- 100Execution cost. Instruction body is 1348 tokens
- low 12 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 319: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 30 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.