AC assess-target-drug-bd-opportunities-ls
Integrate target biology, disease rationale, drug pipeline, clinical, patent, scientific, regulatory, company, and transaction evidence for target or targeted-asset R&D and business-development decisions. Use for target initiation reviews, asset or modality opportunity screens, partnering theses, target landscape updates, and evidence-based go/no-go conditions.
Integrate target biology, disease rationale, drug pipeline, clinical, patent, scientific, regulatory, company, and transaction evidence for target or…
As a process C 55/100 · Has gaps — weak spots: result and completion, failures and branches, 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: 5. 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 55/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 147 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3367 tokens
- 100Running it twice. No mutating operations
- 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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 363: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 147 items
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.