AC search-pubmed
Search biomedical literature on PubMed via NCBI E-Utilities. Use this skill whenever the user needs to search for scientific papers, biomedical articles, life science research, or any PubMed-indexed content. Triggers: 'search literature', 'find papers', 'PubMed', 'NCBI', 'PMID', 'biomedical', 'scientific articles', 'life science', 'organism research', 'gene/disease/drug papers'. Also use for any mention of searching literature about bacteria, plants, animals, diseases, genes, proteins, drugs, or clinical/biological topics — even if the user doesn't explicitly say 'PubMed'.
Search biomedical literature on PubMed via NCBI E-Utilities.
As a process C 63/100 · Has gaps — weak spots: inputs and preconditions, failures and branches
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 63/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 16 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1073 tokens
- 100Running it twice. No mutating operations
- 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 579: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 16 items
- +3Output format is stated explicitly
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 94.