AB care-decision-family-meeting
Run a family meeting to make a big care decision together — so it's a shared, informed decision instead of a fight or one person deciding alone. Use when asked help me run a family meeting about care, we need to decide together about mom's care, my siblings and I disagree about our parent, or facilitate a care decision. Produces an agenda and structure for the meeting, how to prepare (facts, options, everyone's input), ground rules to keep old family dynamics from derailing it, how to include the person being cared for, ways to work through disagreement toward a decision, and clear next steps with owners — turning an emotional, conflict-prone conversation into a productive one. Not legal, medical, or financial advice.
Run a family meeting to make a big care decision together — so it's a shared, informed decision instead of a fight or one person deciding alone.
As a process B 70/100 · Nearly there — weak spots: when it triggers, failures and branches, 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: 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 70/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 35 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1291 tokens
- 100Running it twice. No mutating operations
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 727: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 35 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.