Skip to content
TrustedSkillsbeta
Back to all skills

Vulnerability Scanning

Checked
aj-geddes·vlatest·security·MIT

This tool automatically identifies potential security weaknesses in your systems and applications, proactively protecting against threats and improving resilience.

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 aj-geddes/useful-ai-prompts --skill vulnerability-scanning -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

aj-geddes

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 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 aj-geddes/useful-ai-prompts at 3f5182cfd7.

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

Commit
3f5182cfd7
Manifest
skills/vulnerability-scanning/SKILL.md
Scanned
6 files, 533 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

vulnerability-scanning

What it does

This skill enables AI agents to automatically scan codebases and infrastructure for known security vulnerabilities, misconfigurations, and weak cryptographic implementations. It leverages tools like Trivy and Semgrep to provide actionable reports on potential risks before deployment.

When to use it

  • Before deploying new containers or images to production environments.
  • During the CI/CD pipeline to block builds containing critical CVEs.
  • When auditing third-party dependencies for outdated or insecure packages.
  • To identify configuration errors in cloud infrastructure-as-code files.

Key capabilities

  • Scans container images and Dockerfiles for vulnerabilities using Trivy.
  • Analyzes codebases for security issues with Semgrep rules.
  • Detects weak cryptographic implementations and hardcoded secrets.
  • Generates structured reports detailing severity levels and remediation steps.

Example prompts

  • "Scan my latest Docker image for any known CVEs and list the high-severity findings."
  • "Run a Semgrep analysis on my Python repository to find potential SQL injection vulnerabilities."
  • "Check my infrastructure-as-code configuration for misconfigurations that expose sensitive data."

Tips & gotchas

Ensure your AI agent has read access to the relevant repositories or container registries before initiating scans. While this skill identifies known issues, it should be combined with manual code reviews and penetration testing for comprehensive security coverage.