Skip to content
TrustedSkillsbeta
Back to all skills

Code Audit Readonly

Checked
jpkovas·vlatest·security

Analyzes code repositories for potential vulnerabilities and style issues without modifying any files.

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 jpkovas/code-audit-readonly --skill code-audit-readonly -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

jpkovas

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 jpkovas/code-audit-readonly at 01940f7d79.

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

Scanned
6 files, 329 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 read-only code auditing capabilities. It can analyze code for potential vulnerabilities, security flaws, and adherence to coding standards without making any modifications to the codebase. The audit focuses on identifying issues rather than automatically fixing them.

When to use it

  • Security Reviews: Before deploying new code or significant updates, assess for common vulnerabilities.
  • Compliance Checks: Verify that code adheres to specific industry regulations or internal coding guidelines.
  • Code Quality Assessment: Identify areas where code can be improved for readability and maintainability.
  • Training & Education: Use the audit results as a learning tool for developers to understand potential pitfalls.

Key capabilities

  • Read-only code analysis
  • Vulnerability detection
  • Security flaw identification
  • Coding standard adherence checks

Example prompts

  • "Audit this Python script for security vulnerabilities: [paste code]"
  • "Analyze this JavaScript file and report any potential coding style violations."
  • "Can you review this C++ code snippet for memory leaks?"

Tips & gotchas

The skill is read-only; it will not modify the provided code. The accuracy of the audit depends on the complexity of the codebase and the specific auditing rules configured.