AD apa7-reference-helper
Format, audit, and polish academic references in APA 7th style, including in-text citations, DOI/URL cleanup, and correction tables for student papers.
Format, audit, and polish academic references in APA 7th style, including in-text citations, DOI/URL cleanup, and correction tables for student papers.
As a process D 49/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (apa7-reference-helper) differs from the folder (apa7-reference-helper-mia956)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 85Steps. 38 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 1185 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 151: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (2 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.