BC jcvd
Authorization gatekeeper for OpenClaw agents. Scoped grants, time-bound permissions, skill scanning, prompt injection detection, and full audit trail. The roundhouse kick your agent needs.
As a process C 56/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.
- 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 · 6
✓ No critical or high findings
Medium and low: 6
-
low Risky intent
intent-offensive-securityREADME.md:67Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Privilege escalation vectors
-
low Dangerous commands
cmd-privilegescan-skill.sh:146Privilege escalation / world-writable permissions (string literal in code, not executed; documentation of a security skill)"chmod 777"
code literalsecurity skill -
low Risky intent
intent-offensive-securitySKILL.md:108Offensive-security / dual-use content (legitimate for authorised testing; review intended use)4. **Privilege escalation** -- Attempts to modify SOUL.md, IDENTITY.md, openclaw.json, or agent configuration
-
low Risky intent
intent-offensive-securitySKILL.md:129Offensive-security / dual-use content (legitimate for authorised testing; review intended use)[PASS|WARN|FAIL] Privilege escalation
A further 2 matches are quotations in this security skill's documentation and are not counted as 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") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 56/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
- 40Consistency. Frontmatter name (jcvd) differs from the folder (jean-claw-van-damme)
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 65Failures and branches. 3 branches
- 100Steps. 83 steps
- 100Execution cost. Instruction body is 2427 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- 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)
- +1No license
- +2Single-language instructions
- +3Description length 188: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 83 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.