AB biomedical-patent-trends
Download, search, and analyze Patent-Mol-Wiki biomedical-patent packages. Use when users ask what happened in a recent patent period, need portfolio or trend statistics from wiki index.md files, ask whether a target, disease, modality, organization, or patent is present, need charts of patent distributions, or need molecular-structure analysis from selected patent folders.
Download, search, and analyze Patent-Mol-Wiki biomedical-patent packages.
As a process B 71/100 · Nearly there — weak spots: result and completion
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: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "credential_files"
Process rating: all ten parameters 71/100
- 0Result and completion. Does not say what the result is
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 17 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 1818 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low The response is described with custom markup (3 tags): a typed call is more reliable
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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 375: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 5 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.