BC pentest-findings-report
Use this skill when an authorized penetration tester, red team operator, or security consultant needs to document and draft findings from a completed authorized engagement into a structured penetration test report. Covers executive summary, technical findings with CVSS scoring, proof-of-concept summaries, impact analysis, remediation roadmap, and appendices. Produces a DRAFT report for lead tester review before client delivery.
Use this skill when an authorized penetration tester, red team operator, or security consultant needs to document and draft findings from a completed…
As a process C 54/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, 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 · 12
✓ No critical or high findings
Medium and low: 12
-
low Risky intent
intent-offensive-securityREADME.md:1Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# pentest-findings-report
-
low Risky intent
intent-offensive-securityREADME.md:3Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Turn authorized penetration test findings into a structured, client-ready report.
-
low Risky intent
intent-offensive-securityREADME.md:13Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- You have completed an authorized penetration test and need to produce the final written deliverable
-
low Risky intent
intent-offensive-securityREADME.md:39Offensive-security / dual-use content (legitimate for authorised testing; review intended use)DRAFT penetration test report (executive summary, engagement overview, risk table, technical findings, remediation roadmap, appendices) for lead tester review before client delivery.
-
low Risky intent
intent-offensive-securityskill-card.md:2Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Use this skill when an authorized penetration tester, red team operator, or security consultant needs to document and draft findings from a completed authorized engagement into a structured penetratio
-
low Risky intent
intent-offensive-securityskill-card.md:14Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Authorized penetration testers, red team operators, and security consultants use this skill to turn completed engagement findings into a draft client report with executive summary, CVSS-scored technic
-
low Risky intent
intent-offensive-securityskill-card.md:29Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- [ClawHub skill page](https://clawhub.ai/archlab-space/pentest-findings-report) <br>
-
low Risky intent
intent-offensive-securitySKILL.md:2Offensive-security / dual-use content (legitimate for authorised testing; review intended use)name: pentest-findings-report
-
low Risky intent
intent-offensive-securitySKILL.md:4Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Use this skill when an authorized penetration tester, red team operator, or security
-
low Risky intent
intent-offensive-securitySKILL.md:6Offensive-security / dual-use content (legitimate for authorised testing; review intended use)into a structured penetration test report. Covers executive summary, technical findings
-
low Risky intent
intent-offensive-securitySKILL.md:11Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# Pentest Findings Report
-
low Risky intent
intent-offensive-securitySKILL.md:13Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Convert raw authorized engagement findings into a structured, client-ready penetration test report aligned to PTES and OWASP Testing Guide documentation standards.
Files scanned: 4. 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 54/100
- 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
- 30Running it twice. 8 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 51 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1409 tokens
- 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)
- +1No license
- +2Single-language instructions
- +3Description length 431: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 51 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.