SKILLEMALL.ai
GitHub ↗ RU Sign in

CC simple-ledger

Log expenses, check balances, track budgets, set savings goals, and monitor stock/fund/ETF investments from natural language. Plain-text CSV storage, multi-account, offline-first with optional real-time quotes via opt-in network access.

ClawHub Agent Skills author: TSAG1 v104.0.1 MIT-0 37 files · 15 scripts body ≈ 2 985 tokens Open the sourceclawhub.ai↗ analyzed 10 d ago

Log expenses, check balances, track budgets, set savings goals, and monitor stock/fund/ETF investments from natural language.

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

ProcedureData and analyticsSoftware developmenttype 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
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
71
Run on models
none yet
Process rating
C
62/100
Has gaps
Inputs and preconditions w 11
0
When it triggers w 12
20
Failures and branches w 10
55
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: 26. 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 frontmatter-key unknown frontmatter key "name_zh"
  • note frontmatter-key unknown frontmatter key "description_zh"
  • note frontmatter-key unknown frontmatter key "triggerWords"

Process rating: all ten parameters 62/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (web, python) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 69 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2985 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • low 13 top-level sections: this looks like several domains in one skill
  • high The skill tells the model to perform an irreversible action with no human approval

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)
  • -236 emoji in the instructions: noise for the model
  • -35 of 9 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 236: enough signal without eating the budget
  • +4Structure: 24 headings
  • +3Step-by-step instructions: 69 items
  • +3Output format is stated explicitly
  • +4Has examples (12 code blocks)
  • +4Reference files are cited in the instructions (8 of 8)

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

External checks

ClawHub: suspicious
This finance skill is mostly coherent, but it needs Review because its scripts do not enforce the declared ledger-folder boundary for some reads and writes.
LLM: suspicious (high) · VirusTotal: · 16 Sept 2026