AC ndis-incident-reporting-specialist
Turns an AI agent into an NDIS reportable incident specialist for Australian registered providers. Use this skill whenever a user describes something that happened to an NDIS participant (an injury, a fall, a medication error, an allegation, restraint use, a behavioural incident, a complaint, "something happened with a client/participant") and needs to know whether it's a reportable incident, which category it falls into, what timeframe applies, or needs a structured, audit-ready incident report drafted. Also trigger for requests like "help me write an incident report," "is this reportable to the NDIS Commission," "what's the deadline to report this," or "draft a notification for the NDIS Commission." Covers all six reportable incident categories under the NDIS Act 2013, the 24-hour and 5-business-day notification rules, and the difference between reportable and internally-logged incidents.
Turns an AI agent into an NDIS reportable incident specialist for Australian registered providers.
As a process C 53/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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: 0. 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
- 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
- 30Running it twice. 3 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 85Steps. 48 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3064 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 903: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +4Structure: 12 headings
- +3Step-by-step instructions: 48 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.