SKILLEMALL.ai
GitHub ↗ RU Sign in

CC skill-usage-stats

只读统计 Claude/Codex 的 Skill 使用证据并检查 agent 配置健康。仅用于明确的健康检查、配置诊断、使用排行或低使用候选请求；会识别 enabled 插件并单列批量审计读取。不要用于规范源、触发、全局/项目/profile/冷存储、投影或退役治理，改用 skill-ecosystem-doctor。忽略引用日志和相邻任务。

majiayu000/spellbook Agent Skills author: majiayu000 MIT 6 files · 5 scripts body ≈ 2 092 tokens Open the sourcegithub.com↗ analyzed 3 d ago

只读统计 Claude/Codex 的 Skill 使用证据并检查 agent 配置健康。仅用于明确的健康检查、配置诊断、使用排行或低使用候选请求；会识别 enabled 插件并单列批量审计读取。不要用于规范源、触发、全局/项目/profile/冷存储、投影或退役治理，改用…

As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
C
54/100
Has gaps
Result and completion w 14
0
When it triggers w 12
20
Inputs and preconditions w 11
30
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: 6. 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")
  • note edit-residue the text marks something as outdated (lines 63, 80, 102, 107): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 54/100

  • 0Result and completion. Does not say what the result is
  • 20When it triggers. No condition that starts the skill
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 2 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
  • 100Steps. 47 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2092 tokens
  • 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
  • -33 of 5 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 173: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 47 items
  • +4Has examples (3 code blocks)

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