AB wisediag-report
Medical Report Interpretation — Interpret medical report images (via local file binary upload or image URL) with AI-powered OCR recognition, abnormal indicator detection, and health advice. Triggered when the user asks to interpret a medical report and provides a local image/PDF file path or image URL. Can also be invoked explicitly: say 'Use WiseDiag Report to interpret this report'.
As a process B 66/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Dangerous commands
cmd-shell-rcREADME.md:31Writes to a shell startup fileecho 'export WISEDIAG_API_KEY=your_api_key_here' >> ~/.zshrc
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "registry" - note
frontmatter-keyunknown frontmatter key "env_vars" - note
frontmatter-keyunknown frontmatter key "credentials"
Process rating: all ten parameters 66/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 60Failures and branches. 2 branches
- 100Tools and files. No external tools needed
- 100Steps. 13 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1422 tokens
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
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 387: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (4 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.