Skip to content
TrustedSkillsbeta
Back to all skills

Pentest Checklist

Listed
sickn33·vlatest·security·MIT

This Pentest Checklist AI generates a comprehensive security audit plan to ensure thorough vulnerability testing and improve system protection.

Repository

Install on your platform

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

  1. 1

    Run this in your project

    terminal
    $ npx skills add sickn33/agentic-awesome-skills --skill pentest-checklist -a claude-code

  2. 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

sickn33

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

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    No SKILL.md was found in the skill's directory.

    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 sickn33/antigravity-awesome-skills at 5a4cdd9df8.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
5a4cdd9df8
Manifest
skills/pentest-checklist/SKILL.md
Scanned
0 files
Copies in repo
3 — all of them scanned
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

The pentest-checklist skill provides a structured framework for AI agents to generate comprehensive penetration testing checklists. It ensures security assessments cover critical phases from reconnaissance to reporting, reducing the risk of overlooked vulnerabilities.

When to use it

  • Pre-assessment planning: Generate a tailored scope and methodology before launching an automated scan or manual audit.
  • Compliance verification: Ensure your testing process aligns with industry standards like PTES, NIST, or OWASP.
  • Team coordination: Distribute a standardized checklist to junior pentesters to maintain consistency across engagements.
  • Gap analysis: Compare current security posture against the checklist items to identify missing controls.

Key capabilities

  • Generates phase-specific tasks for reconnaissance, scanning, exploitation, and post-exploitation.
  • Structures output into clear, actionable steps for human analysts or automation scripts.
  • Adapts checklists based on target environment types (web, network, mobile, cloud).

Example prompts

  • "Create a penetration testing checklist for a public-facing web application following the OWASP Top 10."
  • "Generate a pre-engagement scope document and asset discovery plan for a corporate intranet."
  • "List the key verification steps required after successfully exploiting a SQL injection vulnerability."

Tips & gotchas

Ensure you have explicit authorization before using generated checklists on any live system to avoid legal repercussions. Always customize the output to fit the specific technology stack and risk profile of the target environment.