AC heartbeat-cron
Create and refine HEARTBEAT.md files for murmur — a CLI daemon that runs scheduled Claude prompts on a cron or interval schedule. Use this skill when the user wants to set up a recurring automated action (e.g., "monitor my GitHub issues", "check Hacker News for AI articles", "watch my endpoints", "send me a daily digest"). Guides the user through an interview, drafts the heartbeat prompt, tests it, and registers it with murmur's scheduler. Triggers: heartbeat, murmur, recurring task, scheduled action, cron, monitor, watch, automate, periodic check, scheduled prompt.
As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Exfiltration
exfil-webhook-urlreferences/examples.md:12Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)- **Telegram bot**: `curl -s "https://api.telegram.org/bot$TELEGRAM_TOKEN/sendMessage" -d "chat_id=$CHAT_ID&text=..."`
placeholder -
low Exfiltration
net-credential-usereferences/examples.md:12Credential used in a network call (verify the destination is the intended service) (test fixture / example file; quoted — discussed, not commanded)- **Telegram bot**: `curl -s "https://api.telegram.org/bot$TELEGRAM_TOKEN/sendMessage" -d "chat_id=$CHAT_ID&text=..."`
fixturequoted -
low Exfiltration
exfil-webhook-urlreferences/examples.md:88Webhook / callback URL commonly used for exfiltration (verify the destination) (test fixture / example file; quoted — discussed, not commanded)- Send a Telegram message: `curl -s "https://api.telegram.org/bot{token}/sendMessage" -d "chat_id={id}&text=PR #{number} needs review: {title}"`fixturequoted
Files scanned: 3. 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 59/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 8 branches
- 85Steps. 52 steps, 2 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2468 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
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 4 example trigger phrases
- +3Description length 572: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 52 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.