AC competitive-radar
Tracks competitors weekly across 6 signals: pricing page diffs, homepage positioning changes, blog/RSS posts, job postings (hiring as strategy signal), GitHub star velocity and releases, and daily critical-change alerts for pricing or funding keywords. Delivers a structured digest to Slack, Telegram, WhatsApp, or Discord every Monday. Fires same-day alerts for critical changes. Use when asked to "add competitor", "track competitor", "competitor digest", "what changed at [company]", "competitor report", "monitor [company]", "who is [company] hiring", "did [company] change pricing".
As a process C 52/100 · Has gaps — weak spots: result and completion, when it triggers, 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
exfil-webhook-urlREADME.md:51Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)export DISCORD_WEBHOOK_URL="https://discord.com/api/webhooks/..."
placeholder -
low Exfiltration
exfil-webhook-urlscripts/deliver.py:170Webhook / callback URL commonly used for exfiltration (verify the destination) (the skill's own vendor host; quoted — discussed, not commanded)url = f"https://api.telegram.org/bot{token}/sendMessage"vendor-hostquoted
Files scanned: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "emoji" - note
frontmatter-keyunknown frontmatter key "requires"
Process rating: all ten parameters 52/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 10 mutating operations with no state check
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 70Failures and branches. 4 branches
- 100Steps. 51 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1632 tokens
- 100Progress reporting. Reports progress
- low The response is described with custom markup (13 tags): a typed call is more reliable
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 8 example trigger phrases
- +3Description length 587: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 51 items
- +4Has examples (1 code blocks)
- +3All 8 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.