SKILLEMALL.ai

AD clawhub-stats-tracker

查看 ClawHub 上已发布 Skill 的运营数据(Stars、Downloads、Installs、版本号、发布时间)。 从 ~/.clawhub/tracked-skills.json 读取跟踪列表,通过 clawhub inspect --json 获取实时数据, 支持单个查询、批量查询和按系列筛选。无需登录 ClawHub,inspect 接口公开可用。 触发词:clawhub 数据、skill 数据、发布数据、installs、downloads、skill stats、 查看 skill 安装量、clawhub stats、skill 运营数据。 不适用于:发布 Skill(使用 clawhub publish)、搜索新 Skill(使用 clawhub search)、 安装 Skill(使用 clawhub install)。

ClawHub Agent Skills author: fangshan101-coder v1.0.0 MIT-0 3 files · 1 script body ≈ 663 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ReferenceInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
D
43/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. 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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

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
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
  • 100Steps. 5 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 663 tokens

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
  • +1No license
  • +2Single-language instructions
  • +3Description length 378: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 5 items
  • +4Has examples (7 code blocks)
  • +3All 1 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.

External checks

ClawHub: suspicious
This skill is mostly a read-only ClawHub stats viewer, but its recommended script can execute unsafe code if the local tracked-skills config contains a crafted slug.
LLM: suspicious (high) · VirusTotal: · 29 May 2026