Skip to content
TrustedSkillsbeta
Back to all skills

Security Analyzer

Listed
cornjebus·vlatest·security·MIT

Identifies potential vulnerabilities and misconfigurations in systems and code using advanced analysis techniques.

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 cornjebus/security-analyzer --skill security-analyzer -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

cornjebus

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.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: api.osv.dev.

    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.

    Hosts contacted

    api.osv.devundeclared

    What it found

    • .claude/skills/security-analyzer/scripts/fetch_vulns.py:14contacts api.osv.dev
      OSV_API = "https://api.osv.dev/v1/query"

  • 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 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 cornjebus/security-analyzer at db38bd9df7.

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

Commit
db38bd9df7
Manifest
.claude/skills/security-analyzer/SKILL.md
Scanned
5 files, 1,058 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 security-analyzer skill assesses provided text for potential security vulnerabilities, such as SQL injection or cross-site scripting (XSS). It identifies risky patterns and suggests remediation strategies. This helps developers proactively improve code security and reduce attack surfaces.

When to use it

  • Reviewing user input validation routines in web applications.
  • Analyzing configuration files for exposed credentials or insecure settings.
  • Examining SQL queries for potential injection vulnerabilities.
  • Auditing JavaScript code for XSS risks.

Key capabilities

  • Vulnerability detection (SQL Injection, XSS)
  • Pattern identification of risky code constructs
  • Remediation suggestions

Example prompts

  • "Analyze this PHP code snippet for SQL injection vulnerabilities: [code snippet]"
  • "Can you find any potential XSS risks in this JavaScript function? [JavaScript function]"
  • "Review the following configuration file and identify any security concerns. [Configuration File Content]"

Tips & gotchas

The accuracy of the analysis depends heavily on the quality and completeness of the provided code or text. It's best used as a supplementary tool alongside other security practices, not a replacement for thorough manual review.