AC statb-dashboard
Push real-time progress and key metrics to a live statb.io dashboard during any long-running task. Use this skill whenever the agent is performing work that takes multiple steps, iterations, or extended time — such as coding, data processing, batch operations, training loops, deployments, migrations, CI runs, scraping, file conversions, or any multi-step automation. The agent should push numeric progress indicators (steps completed, items processed, errors encountered, percentages, durations, counters) to statb.io so the user can monitor progress in real time from a browser without interrupting the agent. Trigger phrases: "push to dashboard", "monitor progress", "track metrics", "show me a live board", "report status to statb", "use statb", "push to statb.io", "keep me updated on progress".
As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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: 2. 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 52/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 26 mutating operations with no state check
- 40Consistency. Frontmatter name (statb-dashboard) differs from the folder (statb)
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 24 steps
- 100Execution cost. Instruction body is 1297 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +3Description length 801: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 8 example trigger phrases
- +4Structure: 12 headings
- +3Step-by-step instructions: 24 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.