AD skill-security
Security checks for installing skills, packages, or plugins. Use BEFORE any `npm install`, `openclaw plugins install`, `clawhub install`, or similar install commands. Also use when reviewing a newly installed skill before first use. Triggered by any install, add, or package addition request.
Security checks for installing skills, packages, or plugins.
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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 Risky intent
intent-offensive-securitySKILL.md:89Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- **AuthTool** — dormant payload, activates on specific natural language prompts, establishes reverse shell
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 43/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (skill-security) differs from the folder (skill-security-scan)
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 100Steps. 51 steps
- 100Execution cost. Instruction body is 1199 tokens
- 100Running it twice. Mutating operations check current state
- 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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -217 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 292: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 51 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.