AB Remind
Reminds the user of commitments they already know — meetings, deadlines, bills, promises, follow-ups — at the right lead time, in their style. Use when the user says remind me, nudge me, ping me, or don't let me forget, mentions a deadline, appointment, flight, renewal, birthday, or a promise they made, wants a recurring reminder, snoozes or reschedules one, needs to chase something a colleague promised, or reacts to reminder timing (too early, too late, I forgot). Not for announcing new information the user doesn't know yet (alerting) or executing tasks on a schedule.
As a process B 77/100 · Nearly there — weak spots: inputs and preconditions, running it twice
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: 5. 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) - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "changelog" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 77/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 13 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 65Failures and branches. 3 branches
- 100Tools and files. No external tools needed
- 100Steps. 32 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 2292 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 575: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 32 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.