AF wedding-logistics-planner
Plan the wedding day as the operation it is — the minute-level run sheet, the vendor call sheet, the who-handles-problems roster, and the buffer discipline that keeps the couple out of logistics on the day. Use when asked make our wedding day timeline, day-of run sheet, who tells the vendors where to go, or how do we not deal with problems at our own wedding. Produces the run sheet with buffers, the vendor call sheet, the delegation roster with a named day-of decision-maker, and the contingency cards for the classic failures.
Plan the wedding day as the operation it is — the minute-level run sheet, the vendor call sheet, the who-handles-problems roster, and the buffer discipline…
As a process F 54/100 · Will not run — References files that are not bundled: ../sun-and-moon/SKILL.md, ../wedding-vendor-contract-decoder/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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
- warning
missing-refreference to a missing file: ../sun-and-moon/SKILL.md - warning
missing-refreference to a missing file: ../wedding-vendor-contract-decoder/SKILL.md
Process rating: all ten parameters 54/100
- 0Tools and files. 2 referenced file(s) missing: ../sun-and-moon/SKILL.md, ../wedding-vendor-contract-decoder/SKILL.md
- 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
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 23 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1361 tokens
- low 10 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
- +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 531: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 23 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.