AB interpretive-lab-comment-drafter
Use this skill when a clinical laboratory scientist (MLS/MT/CLS), pathologist, or lab director needs to draft an interpretive comment for a complex laboratory panel result — including CBC with differential, CMP, hepatic function panel, thyroid panel, lipid panel, coagulation studies, or urinalysis. Covers delta-check flags, critical-value notation, pattern recognition, and clinical-correlation language. Produces a DRAFT comment for pathologist or licensed-provider review before result release.
Use this skill when a clinical laboratory scientist (MLS/MT/CLS), pathologist, or lab director needs to draft an interpretive comment for a complex laboratory…
As a process B 69/100 · Nearly there — weak spots: inputs and preconditions, progress reporting
How to improve
- 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
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 69/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 57 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2819 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
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 498: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 57 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.