Skip to content
TrustedSkillsbeta
Back to all skills

Repository Analyzer

Checked
lv416e·vlatest·backend

Analyzes code repositories to identify potential vulnerabilities and code quality issues, boosting security & maintainability.

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 lv416e/dotfiles --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

lv416e

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 lv416e/dotfiles at d182953f5e.

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

Scanned
5 files, 1,438 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 lv416e-repository-analyzer skill analyzes code repositories. It provides insights into project structure, file types, and potentially identifies patterns within the codebase. This allows users to understand a repository's contents without manual inspection or cloning.

When to use it

  • Quick Project Overview: Get a high-level understanding of an unfamiliar open-source project before diving in.
  • Codebase Assessment: Evaluate the complexity and organization of a code repository for potential contributions or audits.
  • File Type Identification: Determine the programming languages and file types used within a large codebase.
  • Repository Exploration: Investigate the contents of a repository without needing to download it locally.

Key capabilities

  • Analyzes code repositories
  • Provides insights into project structure
  • Identifies file types

Example prompts

  • "Analyze this GitHub repository: [repository URL]"
  • "What are the primary programming languages used in this repository? [repository URL]"
  • "Describe the directory structure of this repository. [repository URL]"

Tips & gotchas

The skill's effectiveness depends on the accessibility and size of the target repository. Very large repositories may take a significant amount of time to analyze.