BC self-guardian
Lightweight self-monitoring and self-constraining rules to prevent accidental file deletions, dangerous commands, and risky operations. Activates automatically on file/shell operations.
As a process C 55/100 · Has gaps — 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.
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Dangerous commands
cmd-privilegeSKILL.md:107Privilege escalation / world-writable permissions (documentation table row; documentation of a security skill)| `chmod 777` | World-writable permissions | Use minimal permissions (`644`/`755`) |
tablesecurity skill -
low Dangerous commands
cmd-pipe-to-shellSKILL.md:116Downloads and executes remote code from an unrecognised host (pipe to shell) (documentation table row; documentation of a security skill)| `curl <url> \| sh` | Arbitrary code execution | Download, inspect, then run |
tablesecurity skill
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") - note
frontmatter-keyunknown frontmatter key "activation"
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 27 mutating operations with no state check
- 60Tools and files. Uses tools (bash, read, web, git, python, node) that frontmatter does not declare
- 100Steps. 44 steps
- 100Failures and branches. 9 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1895 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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 185: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 44 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.
External checks
ClawHub: clean
This is an instruction-only safety skill that adds extra caution around file edits and shell commands, with some likely over-triggering and a privacy caveat to watch for.
LLM: benign (high) · VirusTotal: · 29 May 2026