BD skill-tracker
通用技能使用统计追踪器,支持 Python 和 Node.js 技能,自动记录调用次数、成功率,生成使用排行榜。数据本地存储,保护隐私。
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
ProcedureSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "changelog"
Process rating: all ten parameters 43/100
- 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 (skill-tracker) differs from the folder (skill-tracker-aiyst)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 36 steps
- 100Execution cost. Instruction body is 747 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 14 top-level sections: this looks like several domains in one skill
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)
- +3Description length 68: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -217 emoji in the instructions: noise for the model
- +2Single-language instructions
- +4Structure: 21 headings
- +3Step-by-step instructions: 36 items
- +4Has examples (7 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.
External checks
ClawHub: clean
This is a local skill-usage tracker that matches its stated purpose, but it creates persistent local logs that may include user, session, and error metadata.
LLM: benign (high) · VirusTotal: · 29 May 2026