BC nmap-pentest-scans-hardened
Plan and orchestrate authorized Nmap host discovery, port and service enumeration, NSE profiling, and reporting artifacts for in-scope targets.
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
ProcedureData and analyticsSecurityInfrastructuretype and topics are labelled automatically from the skill text
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 · 13
✓ No critical or high findings
Medium and low: 13
-
low Risky intent
intent-offensive-securityreferences/tools.md:1Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# Nmap Pentest Scans Tools
-
low Risky intent
intent-offensive-securitySAFETY.md:1Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# nmap-pentest-scans — Safety Evaluation
-
low Risky intent
intent-offensive-securitySAFETY.md:45Offensive-security / dual-use content (legitimate for authorised testing; review intended use)> python skills/nmap-pentest-scans/scripts/nmap_pentest_scans.py \
-
low Risky intent
intent-offensive-securitySAFETY.md:125Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)> 1. **I don't execute offensive tooling** — Even for legitimate penetration testing, I can't run password-cracking, service-bruiting, or exploit tools directly.
quoted -
low Risky intent
intent-offensive-securitySAFETY.md:176Offensive-security / dual-use content (legitimate for authorised testing; review intended use)> python skills/nmap-pentest-scans/scripts/nmap_pentest_scans.py \
-
low Risky intent
intent-offensive-securitySAFETY.md:207Offensive-security / dual-use content (legitimate for authorised testing; review intended use)> # Nmap Pentest Scans - Scope Clarification
-
low Risky intent
intent-offensive-securityskill-card.md:29Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- [Nmap Pentest Scans Tools](references/tools.md) <br>
-
low Risky intent
intent-offensive-securityskill-card.md:35Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- [ClawHub skill page](https://clawhub.ai/snazar-faberlens/nmap-pentest-scans-hardened) <br>
-
low Risky intent
intent-offensive-securitySKILL.md:2Offensive-security / dual-use content (legitimate for authorised testing; review intended use)name: nmap-pentest-scans-hardened
-
low Risky intent
intent-offensive-securitySKILL.md:6Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# Nmap Pentest Scans
-
low Risky intent
intent-offensive-securitySKILL.md:27Offensive-security / dual-use content (legitimate for authorised testing; review intended use)python skills/nmap-pentest-scans/scripts/nmap_pentest_scans.py --scope scope.json --target <target> --input <path> --output <path> --format json --dry-run
-
low Risky intent
intent-offensive-securitySKILL.md:35Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)- `findings/nmap-pentest-findings.json`
quoted -
low Risky intent
intent-offensive-securitySKILL.md:36Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)- `nmap-pentest-scans-report.json`
detector
Files scanned: 7. 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 53/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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 18 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 547 tokens
- 100Running it twice. No mutating operations
- 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
- +1No license
- +2Single-language instructions
- +3Description length 143: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.
External checks
ClawHub: suspicious
This Nmap scanning skill is mostly upfront about authorized security testing, but its prompts and references leave too much room for unsafe or out-of-scope network scans.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026