BD runvouch
Watchdog for this OpenClaw agent: report run start/end, evidence and cost to RunVouch so missed runs, loops and runaway spend alert you on Telegram.
Watchdog for this OpenClaw agent: report run start/end, evidence and cost to RunVouch so missed runs, loops and runaway spend alert you on Telegram.
As a process D 47/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 Exfiltration
net-credential-useSKILL.md:15Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)`curl -X POST $RUNVOUCH_URL/v1/agents -H "X-API-Key: $RUNVOUCH_KEY" -H "Content-Type: application/json" -d '{"name":"openclaw-main","cadence_s":900,"grace_s":300,"cap_day_cost":10,"evidence_required":quoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Watchdog for this OpenClaw agent: report run start/end, evidence a… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 47/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 75Steps. 3 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 395 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 148: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 3 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.