AB church-event-planner
Plan and manage church events from start to finish with church-specific intelligence: ministry team coordination, volunteer rotation tracking, sermon series alignment, and liturgical calendar awareness. Use this skill whenever someone mentions planning a church event, gathering, retreat, VBS, potluck, fundraiser, conference, special service, wedding, funeral, community outreach, ministry team scheduling, or any ministry event. Trigger on casual phrases too: 'we need to start planning Easter,' 'who's handling VBS this year,' 'I need a caterer for the banquet,' 'who's on greeter rotation Sunday,' 'is Sarah getting burned out,' 'what's coming up in Lent,' 'can the worship team handle this,' 'tie this to the current sermon series,' 'can you help me think through this event,' or 'what still needs to get done for Sunday' should all activate this skill.
As a process B 69/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 ≈ 6322 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 69/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 26 mutating operations with no state check
- 60Steps. 112 steps, 4 vague phrases
- 60Result and completion. Output format stated, no completion criterion
- 65Failures and branches. 3 branches
- 70Execution cost. Instruction body is 6322 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
- low 13 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)
- +3Description length 858: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 53 headings
- +3Step-by-step instructions: 112 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.