BA ministry-weekly
Use this skill when a church staff user is actively producing weekly Sunday content. Specific triggers: 'generate this week's content package,' 'here's the brief for Sunday,' 'sermon this week is [passage/title],' 'we're starting a new sermon series [title],' 'week [N] of the [series] series,' 'what have we covered in this series so far,' 'make me graphics for this week's sermon,' 'draft the weekly church email,' 'draft Sunday's bulletin,' 'social posts for this week's sermon,' 'update my church profile,' or 'send this package to the Telegram channel.' Do NOT trigger on casual mentions of church-related topics, personal religious questions, theology discussions, or general scripture lookups outside a weekly-content-production context. Covers: bulletin drafting, scripture context blocks with cross-references, platform-specific social posts (Facebook, Instagram, X, Threads, community group), the weekly church email, AI image generation prompts anchored to the series' graphics theme, sermon-series threading and recaps, and (optional) Telegram channel delivery of the assembled package. Persists church profile, sermon series history, and weekly briefs to a local JSON file.
As a process A 80/100 · Runs to the end — weak spots: inputs and preconditions
How to improve
- Shorten the description to 1024 characters.
- 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
- error
description-longdescription is 1186 chars, limit 1024
Process rating: all ten parameters 80/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 60Result and completion. Output format stated, no completion criterion
- 70Failures and branches. 10 branches
- 100Tools and files. No external tools needed
- 100Steps. 64 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3988 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
- medium 3 test cases, all positive: not one "should refuse" or "should ask first"
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 1186: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 27 headings
- +3Step-by-step instructions: 64 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.