Skip to content
TrustedSkillsbeta
Back to all skills

Ghost Validate

Checked
ghostsecurity·vlatest·other·Apache-2.0

Ghost-validate silently assesses application security posture against best practices without disrupting live operations.

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 ghostsecurity/skills --skill ghost-validate -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

ghostsecurity

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 ghostsecurity/skills at 6ea8e3ba66.

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

Commit
6ea8e3ba66
Manifest
plugins/ghost/skills/validate/SKILL.md
Scanned
2 files, 109 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

The Ghost Validate skill assesses security findings to determine if they are true positives or false positives. It analyzes provided finding data, examines relevant source code, and optionally performs live validation using a proxy tool (Reaper) to confirm exploitability. The skill then classifies the finding as True Positive, True Positive (Confirmed), False Positive, or Inconclusive, providing supporting evidence and recommendations.

When to use it

  • When you have received a security vulnerability report from a scanner and want to verify its accuracy.
  • To reduce noise in your vulnerability management process by filtering out false positives.
  • To understand the root cause of a reported vulnerability and inform remediation efforts.

Key capabilities

  • Finding Analysis: Extracts key information from provided findings, including vulnerability class, claim, affected endpoint, code location, and existing validation evidence.
  • Source Code Review: Analyzes source code to verify the specific claim made in the finding, looking for indirect protections or unreachable code paths.
  • Live Validation (Optional): Uses a proxy tool (Reaper) to interact with a live application instance and attempt exploitation of the reported vulnerability.
  • Classification & Reporting: Classifies findings as True Positive, True Positive (Confirmed), False Positive, or Inconclusive, providing detailed evidence summaries, code analysis, and recommendations.

Example prompts

  • "Validate this security finding: [paste finding text here]"
  • "Can you assess the validity of a vulnerability report located at /path/to/finding.txt?"
  • “I have a potential SQL injection issue reported; can you validate it?”

Tips & gotchas

  • The skill requires access to the application's source code for accurate analysis.
  • Live validation is optional and requires a live, accessible instance of the application.
  • For inconclusive findings, be prepared to provide additional information or context to help the skill reach a determination.