AB ndis-progress-note-claiming
Write audit-safe NDIS progress notes with goal referencing, generate compliant shift note templates, identify correct support catalogue line item codes, and troubleshoot NDIS claiming errors for Australian registered and unregistered providers.
Write audit-safe NDIS progress notes with goal referencing, generate compliant shift note templates, identify correct support catalogue line item codes, and…
As a process B 69/100 · Nearly there — weak spots: inputs and preconditions, execution cost, running it twice
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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
- warning
body-longSKILL.md body ≈ 11932 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage" - note
edit-residuethe text marks something as outdated (lines 374): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 69/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 40Execution cost. Instruction body is 11932 tokens: crowds the task out of the window
- 60Steps. 154 steps, 5 vague phrases
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 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
- -221 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 244: enough signal without eating the budget
- +4Structure: 34 headings
- +3Step-by-step instructions: 154 items
- +3Output format is stated explicitly
- +4Has examples (14 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.