BC daily_devotion
Creates personalized daily devotions with verse of the day, pastoral message, structured prayer, and time-aware greetings
As a process C 55/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "npm" - note
frontmatter-keyunknown frontmatter key "repository" - note
frontmatter-keyunknown frontmatter key "requirements"
Process rating: all ten parameters 55/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 11 mutating operations with no state check
- 40Consistency. Frontmatter name (daily_devotion) differs from the folder (daily-devotion)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 4867 tokens
- 100Steps. 219 steps
- 100Failures and branches. 6 branches, has a failure section
- 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
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 121: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 219 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.
External checks
ClawHub: suspicious
This devotional skill is not clearly malicious, but it asks users to run unpinned npm/npx code that was not included in the reviewed artifact.
LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026