AC agent-sentinel
Evaluate-before-Execute (EBE) guardrail for OpenClaw agents. Issues a mandatory GO / NO-GO decision before any high-stakes tool call. Enforces child-safety policy (Global Safety) and travel preferences (budget, night-flight ban, blocked airlines) from SENTINEL_CONFIG.md.
As a process C 62/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency
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: 6. 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 62/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (agent-sentinel) differs from the folder (vigilance)
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 17 steps
- 100Failures and branches. 8 branches, has a failure section
- 100Execution cost. Instruction body is 1667 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)
- +1No license
- +2Single-language instructions
- +3Description length 271: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 17 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.
External checks
ClawHub: suspicious
This looks like a safety guardrail, but it has conflicting packaged skill identities and can send sensitive tool-call details to LLM providers or logs with insufficient privacy scoping.
LLM: suspicious (high) · VirusTotal: · 29 May 2026