BB trustlog-guard
Financial governance for OpenClaw agents. Tracks API spend, enforces budget limits, detects runaway loops, delivers cost briefings. Reads session .jsonl logs locally. 100% private.
As a process B 69/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice
IntegrationInfrastructureAI and agentstype and topics are labelled automatically from the skill text
How to improve
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 69/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 52 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Failures and branches. 10 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2162 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)
- -220 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 180: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 52 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.
External checks
ClawHub: clean
This skill is a local cost-reporting helper that reads OpenClaw session logs and stores a small local budget file, with no evidence of network transfer, hidden execution, or destructive behavior.
LLM: benign (high) · VirusTotal: benign · 28 May 2026