AC watchboard
Query Watchboard intelligence dashboards (watchboard.dev) for structured event data, casualties, KPIs, contested claims, and daily digests across 51+ trackers covering conflicts, politics, culture, and science. Use when: (1) user asks about current events covered by a Watchboard tracker (Iran conflict, Gaza, Ukraine, Sinaloa, etc.), (2) user wants structured intelligence data instead of web search, (3) user asks for casualty figures, KPIs, or contested claims about tracked events, (4) user wants a briefing or summary of a tracked topic. NOT for: topics not covered by any tracker, breaking news less than ~24h old (data updates nightly at 6 AM UTC).
Query Watchboard intelligence dashboards (watchboard.dev) for structured event data, casualties, KPIs, contested claims, and daily digests across 51+ trackers…
As a process C 53/100 · Has gaps — weak spots: result and completion, inputs and preconditions, 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 · 0
✓ No critical or high findings
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 53/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 85Steps. 18 steps, 2 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1013 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (12 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
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 655: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (1 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.