BB performing-vulnerability-scanning-with-nessus
Performs authenticated and unauthenticated vulnerability scanning using Tenable Nessus to identify known vulnerabilities, misconfigurations, default credentials, and missing patches across network infrastructure, servers, and applications. The scanner correlates findings with CVE databases and CVSS scores to produce prioritized remediation guidance. Activates for requests involving vulnerability scanning, Nessus assessment, patch compliance checking, or automated vulnerability detection.
Performs authenticated and unauthenticated vulnerability scanning using Tenable Nessus to identify known vulnerabilities, misconfigurations, default…
As a process B 75/100 · Nearly there — weak spots: failures and branches
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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Risky intent
intent-offensive-securitySKILL.md:38Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Conducting initial vulnerability assessment during the reconnaissance phase of a penetration test
-
low Risky intent
intent-offensive-securitySKILL.md:44Offensive-security / dual-use content (legitimate for authorised testing; review intended use)**Do not use** as a substitute for manual penetration testing, against systems without written authorization, or against fragile systems (medical devices, legacy SCADA) where scanning may cause servic
-
low Risky intent
intent-offensive-securitySKILL.md:63Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)- **Plugin configuration**: Enable all plugin families relevant to the target environment. For penetration testing, ensure "Denial of Service" plugins are disabled unless explicitly authorized. Enable
detector -
low Risky intent
intent-offensive-securitySKILL.md:104Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)- Add context from manual validation (e.g., "This finding was confirmed exploitable during the penetration test")
quoted
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "domain" - note
frontmatter-keyunknown frontmatter key "subdomain" - note
frontmatter-keyunknown frontmatter key "nist_csf" - note
frontmatter-keyunknown frontmatter key "mitre_attack" - note
edit-residuethe text marks something as outdated (lines 11, 110): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 75/100
- 0Failures and branches. Linear process with no failure handling
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 51 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2608 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
- -41 reference files, but SKILL.md never points to them: the model will not open them
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 492: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 51 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.