BD github-track
追踪指定 GitHub 仓库的动态信息,包括 star 数量、issues、PR 变化。 使用场景: - "追踪 xxx 仓库" - "监控 xxx 项目的 star" - "看看 xxx 有什么新 issue" - "检查 xxx 仓库最近有什么 PR" - "github-track xxx/repo"
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Dangerous commands
cmd-cron-mentionREADME.md:66Mentions editing / listing crontabcrontab -e
-
low Dangerous commands
cmd-background-processREADME.md:76Starts a background / autostarted processsystemctl enable github-track.timer
Files scanned: 4. 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")
Process rating: all ten parameters 46/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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 14 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 862 tokens
- 100Running it twice. No mutating operations
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)
- +3Output format is not stated: the model decides each time
- -32 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 154: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.
External checks
ClawHub: suspicious
This skill mostly does GitHub repository tracking, but it includes under-disclosed Slack posting and broad credential guidance that users should review before installing.
LLM: suspicious (high) · VirusTotal: · 29 May 2026