Skip to content
TrustedSkillsbeta
Back to all skills

Analyze Repo

Checked
miles990·vlatest·backend·MIT

Quickly assesses a Git repository's size, commit history, contributors, and potential code quality issues.

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 miles990/claude-software-skills --skill analyze-repo -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

miles990

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 miles990/claude-software-skills at 73632f218e.

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

Commit
73632f218e
Manifest
tools-integrations/analyze-repo/SKILL.md
Scanned
3 files, 1,846 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 analyze-repo skill allows an AI agent to examine a Git repository and provide insights into its contents. It can identify files, directories, and potentially code structure within the repository. This enables automated analysis of project organization and potential areas for improvement or understanding.

When to use it

  • Project onboarding: Quickly understand the layout and key components of a new codebase.
  • Security audits: Identify sensitive file types or configurations present in a repository.
  • Code review preparation: Get an overview of project structure before diving into code changes.
  • Documentation generation: Extract information about files and directories to assist in creating documentation.

Key capabilities

  • Repository analysis
  • File identification
  • Directory listing

Example prompts

  • "Analyze the repository at [repository URL] and list all the top-level directories."
  • "What file types are present in this repository: [repository URL]?"
  • "Can you describe the structure of the project located at [repository URL]?"

Tips & gotchas

The skill requires a valid, publicly accessible Git repository URL as input. Access to private repositories is not supported without appropriate authentication mechanisms (which are outside the scope of this skill).