AB protocol-plan
Generate structured execution plans for medical and molecular biology protocols such as RNA extraction, reverse transcription, qPCR, cell culture, CRISPR, or other healthcare/biomedical procedures.
As a process B 71/100 · Nearly there — weak spots: failures and branches, consistency, progress reporting
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 71/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (protocol-plan) differs from the folder (protocal-plan-skill-for-protocal-agent)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 29 steps
- 100Execution cost. Instruction body is 1197 tokens
- 100Running it twice. No mutating operations
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 197: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 29 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.
External checks
ClawHub: clean
This instruction-only biomedical protocol planning skill is coherent, but users should avoid using it with sensitive local documents or confidential protocol details unless they are comfortable with local reading and web lookups.
LLM: benign (high) · VirusTotal: · 29 May 2026