BC security-audit-owasp
Full OWASP, Nmap, Nikto vulnerability assessment for OpenClaw deployments. Scan your infrastructure, harden configs, and generate compliance reports.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Risky intent
intent-offensive-securityreferences/owasp-checklist.md:8Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- [ ] Test privilege escalation (user → admin)
-
low Risky intent
intent-offensive-securitySKILL.md:6Offensive-security / dual-use content (legitimate for authorised testing; review intended use)tags: [security, owasp, nmap, nikto, vulnerability, audit, pentest, hardening, compliance, infrastructure]
-
low Risky intent
intent-offensive-securitySKILL.md:8Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)trigger: "security audit vulnerability scan penetration test OWASP hardening"
detector
Files scanned: 4. 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 "source" - note
frontmatter-keyunknown frontmatter key "trigger"
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 15 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 283 tokens
- 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
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +2Single-language instructions
- +3Description length 149: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (1 code blocks)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.
External checks
ClawHub: suspicious
This appears to be a legitimate security-audit skill, but it can run active network scans with broad target scope and limited user-facing safeguards.
LLM: suspicious (high) · VirusTotal: · 28 May 2026