SKILLEMALL.ai

BF glm-plan-usage

查询 GLM 编码套餐使用统计,包括配额、模型使用和 MCP 工具使用情况 | Query GLM coding plan usage statistics, including quota, model usage, and MCP tool usage

ClawHub Agent Skills author: OrientLuna v1.0.1 6 files · 1 script body ≈ 1 625 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process F 28/100 · Will not run — References files that are not bundled: LICENSE

ProcedureAI and agentsSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
98
Quality 40%
72
Run on models
none yet
Process rating
F
28/100
Will not run
References files that are not bundled: LICENSE
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
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.
  2. 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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Dangerous commands cmd-cron-mention docs/INSTALLATION.md:292
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-cron-mention docs/INSTALLATION.md:527
    Mentions editing / listing crontab
    crontab -e

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")
  • warning missing-ref reference to a missing file: LICENSE
  • note frontmatter-key unknown frontmatter key "displayName"
  • note frontmatter-key unknown frontmatter key "requirements"

Process rating: all ten parameters 28/100

Will not run. References files that are not bundled: LICENSE
  • 0Tools and files. 1 referenced file(s) missing: LICENSE
  • 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. 5 mutating operations with no state check
  • 40Consistency. Frontmatter name (glm-plan-usage) differs from the folder (openclaw-glm-plan-usage)
  • 100Steps. 29 steps
  • 100Execution cost. Instruction body is 1625 tokens
  • low 12 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)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 128: enough signal without eating the budget
  • +4Structure: 22 headings
  • +3Step-by-step instructions: 29 items
  • +4Has examples (11 code blocks)
  • +4Reference files are cited in the instructions (2 of 2)
  • +3All 1 scripts are documented
  • +1License stated

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

External checks

ClawHub: clean
This skill is a disclosed GLM usage checker, but users should handle the API key and cleanup commands carefully.
LLM: benign (high) · VirusTotal: benign · 28 May 2026