BF Time Tracker / 时间追踪与生产力分析
Natural language time tracking with smart activity classification, multi-dimensional reports, productivity analytics, and billing.
Natural language time tracking with smart activity classification, multi-dimensional reports, productivity analytics, and billing.
As a process F 30/100 · Will not run — References files that are not bundled: scripts/logger.py
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
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: 0. 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) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: scripts/logger.py - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "input_schema" - note
frontmatter-keyunknown frontmatter key "output_schema"
Process rating: all ten parameters 30/100
Will not run. References files that are not bundled: scripts/logger.py
- 0Tools and files. 1 referenced file(s) missing: scripts/logger.py
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (Time Tracker / 时间追踪与生产力分析) differs from the folder (time-guru)
- 85Steps. 12 steps, 1 vague phrases
- 100Execution cost. Instruction body is 1178 tokens
- 100Running it twice. No mutating operations
- 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -42 reference files, but SKILL.md never points to them: the model will not open them
- -31 of 12 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 130: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 51.
External checks
ClawHub: clean
Time Guru is a coherent local time-tracking skill, with disclosed local storage and export behavior, though users should be aware it stores work and billing history on disk.
LLM: benign (high) · VirusTotal: · 16 Jun 2026