Skip to content
TrustedSkillsbeta
Back to all skills

Security

Checked
parcadei·vlatest·security·MIT

Identifies and mitigates potential security threats, vulnerabilities, and unauthorized access attempts within digital environments.

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 parcadei/continuous-claude-v3 --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

parcadei

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 parcadei/continuous-claude-v3 at d07ff4b06b.

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

Commit
d07ff4b06b
Manifest
.claude/skills/security/SKILL.md
Scanned
1 file, 213 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, /security, performs dedicated security audits of code to identify and mitigate potential threats, vulnerabilities, and unauthorized access attempts. It utilizes a two-phase workflow involving aegis for initial scanning and arbiter for verification after fixes are implemented. The focus is on specialized vulnerability patterns, dependency scanning, secret detection, and authentication/authorization review – going beyond general code quality checks.

When to use it

This skill is valuable in the following scenarios:

  • Before handling sensitive data like user information or payment details.
  • After adding security-sensitive features to a codebase.
  • When reviewing authentication code for potential vulnerabilities.
  • To check for injection attacks (SQL, Command, XSS, LDAP).
  • As part of a regular security review process.

Key capabilities

  • Comprehensive Security Scanning: Identifies various vulnerability types including injection attacks, broken authentication, and insecure cryptography.
  • Dependency Scanning: Checks for known vulnerable packages and outdated dependencies.
  • Secret Detection: Identifies hardcoded secrets or credentials within the code.
  • OWASP Top 10 Checks: Performs checks aligned with the OWASP Top 10 security risks.
  • Authentication/Authorization Review: Specifically examines authentication and authorization mechanisms for weaknesses.
  • Verification of Fixes: arbiter verifies implemented fixes and ensures they don't introduce regressions.
  • Scoped Analysis: Allows users to specify the scope of the audit (full codebase, specific area, single file, or dependencies only).

Example prompts

  • /security authentication - Focus security review on authentication-related code.
  • /security src/api/auth.py - Perform a deep dive security audit of src/api/auth.py.
  • /security --deps - Check for vulnerabilities in project dependencies only.

Tips & gotchas

  • The skill is designed for sensitive code and provides more specialized analysis than general code review workflows.
  • After implementing fixes, rerun the skill with the same scope to verify the changes using arbiter.
  • Specify a clear scope (e.g., "the payment processing code") for targeted security audits.