pentest-checklist
Plan Authorized Penetration Tests
Security teams need clear scope, authorization, and follow-up before testing. This skill provides structured checklists for authorized penetration test planning and remediation.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "pentest-checklist" from https://skillstore.io/skills/sickn33-pentest-checklist.md and its manifest at https://skillstore.io/api/skills/sickn33-pentest-checklist/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "pentest-checklist". Plan a five-day web application pentest for a customer portal.
Expected outcome:
- A concise scope with objectives, assets, exclusions, and test window.
- A preparation checklist for accounts, backups, monitoring, and notifications.
- A reporting and remediation plan with owners and retest timing.
Using "pentest-checklist". Help my team prepare monitoring for an approved internal test.
Expected outcome:
The skill produces a monitoring checklist covering authentication logs, application errors, network events, alert routing, and operations contacts.
Using "pentest-checklist". Review our post-test cleanup process.
Expected outcome:
- Remove test accounts and artifacts.
- Restore temporary configuration changes.
- Verify cleanup with logs and owner sign-off.
Security Audit
High RiskMost static backtick findings are Markdown fence false positives, not runtime execution. Real risks remain because the skill documents active scanning, privileged service commands, packet capture, and social engineering or red team planning. These are legitimate for authorized engagements but need stronger guardrails for marketplace use.
Confirmed security concerns (2)
Capability review items (4)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (15)
🌐 Network access (4)
📁 Filesystem access (2)
Detected Patterns
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-pentest-checklist/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-pentest-checklist?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-pentest-checklist?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-pentest-checklist/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-pentest-checklist.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). pentest-checklist security audit report (audit version 5) [Author version 1.1]. Skillstore. https://skillstore.io/skills/sickn33-pentest-checklist/audits/5BibTeX citation
@techreport{sickn33-sickn33-pentest-checklist-2026,
author = {sickn33},
title = {pentest-checklist security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-pentest-checklist/audits/5},
note = {Author version 1.1}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "pentest-checklist security audit report (audit version 5)"
version: "1.1"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/sickn33-pentest-checklist/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-pentest-checklist:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Prepare a Pentest Scope
Create a clear scope, exclusions, objectives, contacts, and approval steps before hiring testers.
Prepare Monitoring and Logs
Plan logging, alerting, backups, and operations communication before an authorized test window.
Track Remediation Follow-Up
Turn test findings into prioritized remediation tasks, retesting plans, and evidence for auditors.
Try These Prompts
Help me outline an authorized penetration test for a web application. Include objectives, in-scope assets, exclusions, timing, and required approvals.
Create a readiness checklist for an approved internal network pentest. Cover accounts, backups, monitoring, communication, and rollback planning.
Compare black box, gray box, and white box approaches for my authorized assessment. Recommend one based on risk, timeline, and available access.
Build a full authorized pentest plan for a regulated environment. Include scope, provider approvals, monitoring, reporting requirements, cleanup, remediation, and retesting.
Best Practices
- Confirm written authorization and scope before using any scanning or testing guidance.
- Prefer staging or controlled test windows for activities that could disrupt production.
- Record approvals, communication paths, findings, remediation owners, and retest dates.
Avoid
- Running scans against assets that are not clearly in scope.
- Changing production systems without an approved rollback and communication plan.
- Treating checklist output as legal approval or proof of safety.