BC voice-to-protocol-transcriber
Record experimental procedures and observations via voice commands during lab work. Real-time transcription for structured experiment documentation.
As a process C 57/100 · Has gaps — weak spots: when it triggers, failures and branches, consistency
ProcedureInfrastructureWriting and documentstype and topics are labelled automatically from the skill text
This is a copy of a skill from another catalog; the rating counts the canonical one: voice-to-protocol-transcriber (ClawHub)
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
For the model run — optional
- 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
description-long-hermesdescription is 148 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - note
frontmatter-keyunknown frontmatter key "status" - note
frontmatter-keyunknown frontmatter key "risk_level" - note
frontmatter-keyunknown frontmatter key "skill_type" - note
frontmatter-keyunknown frontmatter key "owner" - note
frontmatter-keyunknown frontmatter key "reviewer" - note
frontmatter-keyunknown frontmatter key "last_updated"
Process rating: all ten parameters 57/100
- 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
- 40Consistency. Frontmatter name (voice-to-protocol-transcriber) differs from the folder (voice-to-protocol-transcriber-1)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 42 steps
- 100Execution cost. Instruction body is 1192 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 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)
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 148: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 42 items
- +3Output format is stated explicitly
- +4Has examples (7 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.
External checks
ClawHub: suspicious
This skill appears non-malicious, but it needs review because its advertised voice transcription behavior does not match the shipped code and its handling of potentially sensitive lab records is under-scoped.
LLM: suspicious (high) · VirusTotal: · 29 May 2026