AB eulogy-and-obituary-writer
Write a eulogy or obituary for someone you loved when you're grieving and the words won't come — a true, warm piece that sounds like them and like you. Use when asked help me write a eulogy for my father, write an obituary, I have to speak at the funeral, or I don't know what to say about them. Produces a 3-5 minute eulogy or an obituary drafted from your memories rather than cliches, the right structure and length for the setting, and a delivery copy formatted for shaking hands. Gentle process, no interrogation, nothing invented.
Write a eulogy or obituary for someone you loved when you're grieving and the words won't come — a true, warm piece that sounds like them and like you.
As a process B 75/100 · Nearly there — weak spots: when it triggers, progress reporting
The same skill appears in 1 more place: pm-claude-skills
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 75/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 31 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 976 tokens
- 100Running it twice. No mutating operations
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)
- +1No license
- +2Single-language instructions
- +3Description length 536: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 31 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.