AB sleep-science
Complete, self-contained sleep science knowledge base. Use this skill whenever a user asks anything related to sleep timing, sleep debt, naps, caffeine, circadian rhythms, sleep stages, chronotypes, or sleep optimization. An agent with this skill can answer questions like "what time should I sleep if I wake at 6am?", "how much sleep debt do I have?", or "when should I stop drinking coffee?" instantly using the formulas and rules contained here. No external tools needed.
As a process B 71/100 · Nearly there — weak spots: result and completion, execution cost, 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 14398 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "sources"
Process rating: all ten parameters 71/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 5 mutating operations with no state check
- 40Execution cost. Instruction body is 14398 tokens: crowds the task out of the window
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 10 branches
- 100Tools and files. No external tools needed
- 100Steps. 215 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 19 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 474: enough signal without eating the budget
- +4Structure: 68 headings
- +3Step-by-step instructions: 215 items
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.