AB create-life-sciences-patent-report-ls
Create or update a traceable, self-contained HTML patent intelligence report for a life-sciences technology, target, drug, antibody, ADC, company, or patent set. Use when a user requests a life-sciences patent landscape or deep-dive report that integrates claims, sequences or conjugate technology, experiments, pipeline and clinical context, scientific evidence, deals or news, and inline patent-figure evidence.
Create or update a traceable, self-contained HTML patent intelligence report for a life-sciences technology, target, drug, antibody, ADC, company, or patent…
As a process B 71/100 · Nearly there — weak spots: running it twice
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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "copyright"
Process rating: all ten parameters 71/100
- 30Running it twice. 3 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 103 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2925 tokens
- 100Progress reporting. Reports progress
- low 10 top-level sections: this looks like several domains in one skill
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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 413: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 103 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.