AC topic-monitor
Monitor topics of interest and proactively alert when important developments occur. Use when user wants automated monitoring of specific subjects (e.g., product releases, price changes, news topics, technology updates). Supports scheduled web searches, AI-powered importance scoring, smart alerts vs weekly digests, and memory-aware contextual summaries.
Monitor topics of interest and proactively alert when important developments occur.
As a process C 62/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice
The same skill appears in 1 more place: RA-Skills
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 Exfiltration
exfil-webhook-urlREADME.md:185Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)"webhook_url": "https://discord.com/api/webhooks/..."
placeholder -
low Dangerous commands
cmd-cron-mentionscripts/setup_cron.py:146Mentions editing / listing crontab (string literal in code, not executed)print("\nTo verify, run: crontab -l")code literal -
low Exfiltration
exfil-webhook-urlSKILL.md:376Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)"webhook_url": "https://discord.com/api/webhooks/...",
placeholder -
low Dangerous commands
cmd-cron-mentionSKILL.md:532Mentions editing / listing crontab (quoted — discussed, not commanded)- Check cron is running: `crontab -l`
quoted
Files scanned: 11. 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
- 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. 6 mutating operations with no state check
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 80 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3555 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 16 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)
- -32 of 7 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 354: enough signal without eating the budget
- +4Structure: 38 headings
- +3Step-by-step instructions: 80 items
- +3Output format is stated explicitly
- +4Has examples (22 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.