CC voice-post-call
Post-call handling for a voice session — turn the transcript into a brain page, post the summary to the operator's messaging surface, archive the audio. The pipeline is the contract; the firing paths are operator-wired (see "Two firing paths" below for what ships today).
Post-call handling for a voice session — turn the transcript into a brain page, post the summary to the operator's messaging surface, archive the audio.
As a process C 51/100 · Has gaps — References files that are not bundled: people/<slug>.md, companies/<slug>.md, ../voice-persona-mars/SKILL.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: people/<slug>.md - warning
missing-refreference to a missing file: companies/<slug>.md - warning
missing-refreference to a missing file: ../voice-persona-mars/SKILL.md - warning
missing-refreference to a missing file: ../voice-persona-venus/SKILL.md - warning
missing-refreference to a missing file: <url> - note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "mutating" - note
frontmatter-keyunknown frontmatter key "writes_pages" - note
frontmatter-keyunknown frontmatter key "writes_to"
Process rating: all ten parameters 51/100
- 0Tools and files. 5 referenced file(s) missing: people/<slug>.md, companies/<slug>.md, ../voice-persona-mars/SKILL.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 14 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1600 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
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 271: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 14 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.