AB literature-review
Builds or audits a literature review. Produces an evidence map, closest prior work, source clusters, a gap verdict, and a synthesis plan for the introduction. Use when the user asks whether a contribution is novel, who has studied a question, what the literature establishes, how to organize or restructure a review, or wants a reading list, Zotero export, or paper pile turned into a review. Produces a systematic-review protocol scaffold and directs PRISMA or meta-analysis requests to registration, PROSPERO or OSF, and screening tools.
Builds or audits a literature review.
As a process B 69/100 · Nearly there — weak spots: inputs and preconditions
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: 1. 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 69/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 100Steps. 45 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1588 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 539: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 45 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.