Skip to content
TrustedSkillsbeta
Back to all skills

Security

Checked
travisjneuman·vlatest·security·MIT

Analyzes code and systems for vulnerabilities based on travisjneuman's expertise, providing actionable remediation advice.

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 travisjneuman/.claude --skill security -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

travisjneuman

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 travisjneuman/.claude at 050878886e.

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

Scanned
4 files, 3,061 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 provides access to security-related capabilities. It's designed to enhance AI agent interactions with a focus on safety and responsible use. The specific functionalities are not detailed in the provided source, but the core purpose is centered around security considerations within an AI context.

When to use it

  • When you need to evaluate potential risks associated with an AI agent’s actions.
  • To ensure compliance with security protocols or regulations when deploying an AI agent.
  • For generating reports on vulnerabilities and suggesting mitigation strategies for AI systems.
  • During the development process of an AI agent, to proactively address security concerns.

Key capabilities

  • Security-related functionalities (specifics not detailed)
  • Focus on safety and responsible use of AI agents

Example prompts

  • "Analyze this AI workflow for potential security vulnerabilities."
  • "Generate a report outlining the risks associated with using [AI agent name] in a production environment."
  • "Suggest mitigation strategies to address the identified security concerns."

Tips & gotchas

The skill's specific capabilities are not fully defined. Success depends on clear and detailed prompts related to security concerns you want addressed.