BC producer
End-to-end orchestration — the wrapper that drives the whole production contract across roles, plus batch production. Owns when to batch, the shared style lock across a batch, the controlled variation matrix, template extraction, cost rollup, ETA gating, and batch triage. USE WHEN the user asks for a finished result end-to-end ("make me a video, start to finish"), for N >= 3 items ("make 20 videos", "an ad pack batch", "a content farm for X"), to "save this as a template", to "review the batch", or for a cost rollup. TRIGGER (EN): "end to end", "make N videos", "batch", "content farm", "save as a template", "review the batch", "what did this cost".
End-to-end orchestration — the wrapper that drives the whole production contract across roles, plus batch production.
As a process C 57/100 · Has gaps — References files that are not bundled: ../../../docs/playbooks/agent-production-contract.md, ../../../docs/playbooks/unit-lifecycle.md, ../researcher/references/research-bootstrap.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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../../docs/playbooks/agent-production-contract.md - warning
missing-refreference to a missing file: ../../../docs/playbooks/unit-lifecycle.md - warning
missing-refreference to a missing file: ../researcher/references/research-bootstrap.md - warning
missing-refreference to a missing file: ../../../docs/skills-vs-templates.md - warning
missing-refreference to a missing file: ../hyperframes/references/playbook.md - warning
missing-refreference to a missing file: templates/<slug>/ - note
frontmatter-keyunknown frontmatter key "namespace"
Process rating: all ten parameters 57/100
- 0Tools and files. 6 referenced file(s) missing: ../../../docs/playbooks/agent-production-contract.md, ../../../docs/playbooks/unit-lifecycle.md, ../researcher/references/research-bootstrap.md
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 65Failures and branches. 3 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4578 tokens
- 100Steps. 34 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (14 tags): a typed call is more reliable
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 12 example trigger phrases
- +3Description length 656: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 34 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.