SKILLEMALL.ai
GitHub ↗ RU Sign in

BC openclaw-cost-tracker

Track OpenClaw usage costs and provide detailed reports by date and model. Supports daily, weekly, and monthly report formats for Discord and other messaging channels.

ClawHub Agent Skills author: vincentqiu v1.0.2 9 files · 2 scripts body ≈ 372 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 52/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

ReferenceDiscordData and analyticsInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
99
Quality 40%
68
Run on models
none yet
Process rating
C
52/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
When it triggers w 12
20
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Secrets in code secret-high-entropy-token references/JSONL_FORMAT.md:49
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    {"type": "toolCall", "id": "tool…US2", "name": "session_status", "arguments": {}}
    quoted

Files scanned: 9. 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 52/100

  • 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 (openclaw-cost-tracker) differs from the folder (cost-report)
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 8 steps
  • 100Execution cost. Instruction body is 372 tokens
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress

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)
  • -41 reference files, but SKILL.md never points to them: the model will not open them
  • -31 of 2 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 167: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 8 items
  • +3Output format is stated explicitly
  • +4Has examples (2 code blocks)

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

External checks

ClawHub: suspicious
The skill mostly matches its cost-reporting purpose, but its CLI has a real shell-injection flaw and some Discord/error reporting can expose sensitive session-log details.
LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026