AC household-constitution
Turn the household unwritten rules into a short charter everyone actually agreed to — screens, chores, money, guests, quiet — drafted together, with consequences decided in advance and an amendment process so it bends instead of breaking. Use when asked to make family rules that stick, a screen-time agreement, a flatmate agreement, or stop having the same argument about chores. Produces the negotiation session plan, the drafted constitution, the consequence menu agreed before anyone breaks anything, and the review procedure. Works for families and shared houses; slightly funny on purpose, binding on purpose too.
Turn the household unwritten rules into a short charter everyone actually agreed to — screens, chores, money, guests, quiet — drafted together, with…
As a process C 64/100 · Has gaps — weak spots: when it triggers, failures and branches, running it twice
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 64/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
- 30Running it twice. 2 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 29 steps, 2 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1696 tokens
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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 619: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 29 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.