AC biomarker-investigation
Search the academic and patent literatures related to the biomarkers, based on the queries Load the skill when the queries are about - Refer a specific biomarker - If biomarker available for a disease - Techniques and patents related to the biomarker Typical queries - What diseases can creatinine serve as a biomarker? - Searching for biomarkers of cardiovascular disease - Biomarkers for CAR-T therapies. - Search for clinical trials that use transaminases as diagnostic markers.
Search the academic and patent literatures related to the biomarkers, based on the queries Load the skill when the queries are about - Refer a specific…
As a process C 53/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice
The same skill appears in 1 more place: ClawHub
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: 2. 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 53/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Steps. 50 steps, 4 vague phrases
- 60Result and completion. Output format stated, no completion criterion
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3536 tokens
- 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)
- +2Single-language instructions
- +3Description length 481: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 50 items
- +3Output format is stated explicitly
- +4Has examples (10 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.