AB event-planner-os
Plan and manage any event from start to finish, including timelines, task checklists, vendors, volunteers, and budgets. Use this skill whenever someone mentions planning an event, party, gathering, conference, concert, wedding, fundraiser, retreat, shower, dinner party, or any organized occasion. Trigger on casual phrases too -- "I need to plan a birthday party," "the conference is in 8 weeks," "who's our caterer," "what still needs to get done for Saturday," or "how much have we spent on the wedding" should all activate this skill.
As a process B 70/100 · Nearly there — weak spots: inputs and preconditions, running it twice
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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
- warning
body-longSKILL.md body ≈ 6880 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 70/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 59 mutating operations with no state check
- 60Steps. 66 steps, 6 vague phrases
- 60Result and completion. Output format stated, no completion criterion
- 70Failures and branches. 4 branches
- 70Execution cost. Instruction body is 6880 tokens
- 100Tools and files. No external tools needed
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 538: enough signal without eating the budget
- +4Structure: 46 headings
- +3Step-by-step instructions: 66 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.