AB interdisciplinary-care-plan-drafter
Use this skill when a palliative care or hospice interdisciplinary team — including attending physicians, APRNs, RNs, social workers, or chaplains — needs to draft a CMS Conditions of Participation–compliant Interdisciplinary Care Plan (ICP) for a hospice or seriously ill patient. Covers goals-of-care documentation, comfort care plan, IDT role assignments, visit frequencies, and Medicare hospice benefit compliance. Produces a DRAFT for licensed clinician and IDT co-review before any care delivery or billing use.
Use this skill when a palliative care or hospice interdisciplinary team — including attending physicians, APRNs, RNs, social workers, or chaplains — needs to…
As a process B 66/100 · Nearly there — weak spots: when it triggers, progress reporting
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: 4. 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 66/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 80 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3556 tokens
- 100Running it twice. No mutating operations
- 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)
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 517: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 80 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.