Skip to content
TrustedSkillsbeta
Back to all skills

Security Scan

Checked
redpanda-data·vlatest·security

Helps with data, security as part of implementing security and authentication workflows.

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 redpanda-data/console --skill security-scan -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

redpanda-data

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 redpanda-data/console at 0d2c900a21.

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

Commit
0d2c900a21
Manifest
frontend/.claude/skills/security-scan/SKILL.md
Scanned
5 files, 241 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 helps AI agents resolve npm dependency vulnerabilities detected by Snyk.io security scans. It parses vulnerability reports, categorizes them as direct or transitive dependencies, and guides the agent through a workflow of assessment, exploration, fixing, and verification to address these issues within a project's codebase. The skill provides specific rules for handling both direct and transitive dependencies.

When to use it

  • When a user shares Snyk vulnerability reports with the AI agent.
  • When a user mentions CVEs (Common Vulnerabilities and Exposures) or CWEs (Common Weakness Enumerations).
  • When a user asks the agent to fix security issues found in npm dependencies.

Key capabilities

  • Parses Snyk vulnerability reports, extracting information like package name, version, CVE/CWE, severity, and fixed version.
  • Categorizes vulnerabilities as either direct (listed in package.json) or transitive (dependencies of other packages).
  • Checks the project's package.json and lockfile for current and resolved versions.
  • Searches source code for usage of vulnerable packages.
  • Consults the npm registry to find available fixed versions using npm view <package> versions --json.
  • Provides specific rules (vuln-direct-deps.md, vuln-transitive-deps.md) for fixing vulnerabilities.

Example prompts

  • "Can you fix the security vulnerabilities reported by Snyk?"
  • "I have a vulnerability report; can you help me address it?"
  • "What's the best way to resolve this CVE in my project?"

Tips & gotchas

  • When applying fixes, use exact versions for dependencies (avoiding ^ prefixes) to ensure security.
  • Prioritize fixing vulnerabilities with Critical or High severity first.
  • Consider replacing unmaintained packages instead of relying on patches.