Skip to content
TrustedSkillsbeta
Back to all skills

Repository Analyzer

Checked
jackspace·vlatest·backend·MIT

Analyzes code repositories to identify vulnerabilities, code quality issues, and potential risks – crucial for secure development practices.

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 jackspace/claudeskillz --skill repository-analyzer -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

jackspace

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 jackspace/claudeskillz at aef4e299d1.

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

Commit
aef4e299d1
Manifest
skills/repository-analyzer/SKILL.md
Scanned
4 files, 1,487 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

The repository-analyzer skill provides AI agents with the ability to inspect code repositories, extracting structural data and identifying specific files or patterns within a project's history. It enables automated workflows that require understanding the context of software projects without manual file navigation.

When to use it

  • Automatically scanning a new open-source project to generate a summary of its architecture before contributing code.
  • Identifying outdated dependencies or license violations across multiple files in a large monorepo.
  • Extracting specific configuration settings from scattered .env or config files to populate a deployment checklist.
  • Analyzing commit history patterns to detect potential security vulnerabilities introduced during recent updates.

Key capabilities

  • Repository traversal and file discovery
  • Code structure analysis
  • Pattern matching within codebases
  • Historical context retrieval

Example prompts

  • "Analyze the src directory of this repository and list all files containing hardcoded API keys."
  • "Summarize the project structure and identify the primary entry point for the main application module."
  • "Find all instances where the logging module is used with a debug level set to 'error' in this codebase."

Tips & gotchas

Ensure the repository has read access permissions granted to the AI agent before initiating analysis. Large repositories may require longer processing times; consider breaking down requests by specific subdirectories if performance lags.