Pentest Checklist

Name: Pentest Checklist
Author: zebbern

Checked

zebbern·vlatest·security

This Pentest Checklist generates a comprehensive security audit plan, streamlining penetration testing and ensuring thorough coverage.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Installs under a different name. Its SKILL.md names it Pentest Checklist, not the name it is listed under, so the command below uses that name.

Run this in your project

terminal

$ npx skills add zebbern/secops-cli-guides --skill "Pentest Checklist" -a claude-code

Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

zebbern

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned 1 Oct 2026

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned zebbern/secops-cli-guides at f8a9ac70c9.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: f8a9ac70c9
Manifest: skills/pentest-checklist/SKILL.md
Scanned: 1 file, 326 lines

This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.

What each check looks for →

About this skill

What it does

This skill provides a comprehensive pentesting checklist to guide security assessments. It helps ensure thoroughness and consistency in penetration testing procedures, covering various stages from reconnaissance to reporting. The checklist is designed to be adaptable for different environments and attack surfaces.

When to use it

When preparing for a penetration test engagement to ensure all necessary steps are considered.
During a red team exercise to systematically execute attack phases.
As a training tool for security professionals learning about pentesting methodologies.
To create a repeatable and auditable process for vulnerability assessments.

Key capabilities

Provides a structured checklist of penetration testing tasks.
Covers multiple stages of the pentest lifecycle.
Offers a framework for consistent assessment practices.
Adaptable to various environments.

Example prompts

"Generate a pentesting checklist for a web application."
"Show me the reconnaissance phase of the pentest checklist."
“What are the post-exploitation steps in the pentest checklist?”

Tips & gotchas

The skill assumes basic familiarity with cybersecurity concepts and terminology. While adaptable, tailoring the checklist to specific environments may require manual adjustments after generation.