Skip to content
TrustedSkillsbeta
Back to all skills

Owasp Checker

Checked
matteocervelli·vlatest·security·MIT

The Owasp Checker analyzes code for common web security vulnerabilities, safeguarding applications and preventing breaches.

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 matteocervelli/llms --skill owasp-checker --full-depth -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

matteocervelli

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 matteocervelli/llms at 1e1f2089eb.

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

Commit
1e1f2089eb
Manifest
.archive/claude-v1/skills/owasp-checker/SKILL.md
Scanned
1 file, 698 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 owasp-checker skill helps identify potential security vulnerabilities in text based on the OWASP (Open Web Application Security Project) Top Ten. It analyzes provided content and flags instances of common web application security risks like SQL injection, cross-site scripting (XSS), and more. This allows for proactive identification and mitigation of vulnerabilities before deployment.

When to use it

  • Code Review: Analyze code snippets or configuration files for potential OWASP Top Ten vulnerabilities.
  • Content Security Assessment: Evaluate user input fields or dynamically generated content for XSS risks.
  • API Input Validation: Check API request payloads for injection flaws before processing.
  • Security Training: Use it to demonstrate common security weaknesses and educate developers.

Key capabilities

  • OWASP Top Ten vulnerability detection
  • Identification of SQL Injection vulnerabilities
  • Detection of Cross-Site Scripting (XSS) risks
  • Analysis of potential command injection flaws

Example prompts

  • "Check this code for OWASP security vulnerabilities: [code snippet]"
  • "Analyze the following user input field for XSS risks: [user input]"
  • "Can you find any SQL injection possibilities in this API request? [API request]"

Tips & gotchas

The skill's accuracy depends on the complexity of the code or content being analyzed. It is recommended to use it as part of a broader security assessment process, not as a sole solution.