Skip to content
TrustedSkillsbeta
Back to all skills

Security

Checked
tartinerlabs·vlatest·security·MIT

Identifies and remediates potential vulnerabilities in code and infrastructure using advanced static analysis and threat modeling.

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 tartinerlabs/skills --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

tartinerlabs

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 tartinerlabs/skills at a7812b928c.

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

Commit
a7812b928c
Manifest
plugins/security/skills/security/SKILL.md
Scanned
6 files, 254 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 enables an AI agent to perform security audits and identify potential vulnerabilities in code and infrastructure using GitLeaks, a static analysis tool. It scans codebases against predefined rules covering areas like OWASP Top 10 vulnerabilities, hardcoded secrets, authentication issues, insecure dependencies, and data protection concerns. The skill also provides guidance on setting up GitLeaks within a project's pre-commit workflow.

When to use it

  • When performing regular security audits of code repositories.
  • To identify and remediate potential vulnerabilities before deployment.
  • During development to catch security issues early in the process.
  • To ensure compliance with security best practices by scanning for hardcoded secrets or insecure dependencies.

Key capabilities

  • Static Analysis: Scans codebase using predefined rules.
  • Vulnerability Identification: Detects patterns related to OWASP Top 10, hardcoded secrets, authentication issues, insecure dependencies, and data protection concerns.
  • GitLeaks Setup Guidance: Provides instructions for configuring GitLeaks in a project's pre-commit hook (requires Husky + lint-staged).
  • Reporting: Generates reports summarizing findings by severity level (HIGH, MEDIUM) and category.
  • Historical Scan (Optional): Can scan the commit history for vulnerabilities when using the --scan-history flag.

Example prompts

  • "Run a security audit on this repository."
  • "Scan this codebase for hardcoded secrets."
  • "Check for OWASP Top 10 vulnerabilities in src/api/users.ts."
  • "What are the potential data protection issues in my project?"

Tips & gotchas

  • This skill assumes GitLeaks is already installed on the system.
  • The workflow relies on Husky and lint-staged for pre-commit hooks (primarily applicable to JavaScript/TypeScript projects).
  • To perform a historical scan, you must explicitly pass the --scan-history flag during execution.