AC daily-rhythm
Automated daily planning and reflection system with morning briefs, wind-down prompts, sleep nudges, and weekly reviews. Use when the user wants to set up a structured daily routine, morning briefings, evening reflection prompts, or weekly planning sessions. Triggers include requests for daily schedules, morning briefs, wind-down routines, sleep reminders, weekly reviews, productivity systems, or daily planning automation.
Automated daily planning and reflection system with morning briefs, wind-down prompts, sleep nudges, and weekly reviews.
As a process C 62/100 · Has gaps — weak spots: result and completion, running it twice, progress reporting
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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Dangerous commands
cmd-cron-mentionreferences/CONFIGURATION.md:63Mentions editing / listing crontabcrontab -e
-
low Dangerous commands
cmd-cron-mentionreferences/CONFIGURATION.md:192Mentions editing / listing crontab (quoted — discussed, not commanded)- Check cron is installed: `crontab -l`
quoted -
low Dangerous commands
cmd-cron-mentionSKILL.md:83Mentions editing / listing crontabcrontab -e
-
low Dangerous commands
cmd-cron-mentionSKILL.md:212Mentions editing / listing crontab (quoted — discussed, not commanded)- Verify cron is installed: `crontab -l`
quoted
Files scanned: 7. 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 62/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 7 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 74 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1677 tokens
- 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 426: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 74 items
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.