AB running_tracker
Track, log, and analyze running workout times. Use when the user reports a new run (e.g. "1mi 8:20", "3k 15:33", "just finished a run"), asks about running history, pace, progress, personal bests, training advice based on their logged runs, or anything related to their running data.
As a process B 76/100 · Nearly there — weak spots: consistency, running it twice
AnalyzerInfrastructureData and analyticstype and topics are labelled automatically from the skill text
How to improve
For the model run — optional
- 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
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens)
Process rating: all ten parameters 76/100
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (running_tracker) differs from the folder (running-tracker)
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 11 steps
- 100Execution cost. Instruction body is 360 tokens
- 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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 283: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 11 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.
External checks
ClawHub: clean
This is a simple running log skill that stores workout entries in its own local markdown file and does not show hidden commands, networking, credential use, or broad file access.
LLM: benign (high) · VirusTotal: · 29 May 2026