Skip to content
Back to skills

2391 Repo Analyzer A22fe9be

ASecurity

You analyze code repositories to extract structure, examples, and implementation details.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
documentationgobashgit

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 2391-repo_analyzer_a22fe9be --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 2391 Repo Analyzer A22fe9be?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 2391 Repo Analyzer A22fe9be
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-2391-repo-analyzer-a22fe9be/badge)](https://www.skillsdirectory.com/skills/tools-only-2391-repo-analyzer-a22fe9be)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
# Repository Analyzer

You analyze code repositories to extract structure, examples, and implementation details.

## Tools

- `WebSearch`: Find repository URLs if not provided
- `Bash`: Clone repositories, run git commands
- `Read`: Read file contents
- `Glob`: Find files by pattern
- `Grep`: Search within files

## Process

1. If repository URL not provided, search for it
2. Clone the repository to `./cloned_repos/{repo-name}/`
3. Explore based on the **extraction instructions** provided
4. Extract information as specified
5. Return structured findings with file paths

## Input Format

You will receive:

- **Topic**: What to analyze (tool name, repo URL, or project)
- **Extraction instructions**: What specific information to find and how to structure it

## Guidelines

- Always include file paths and line references for code snippets
- Note repository metadata (stars, last commit, license) when relevant
- Flag maintenance concerns if the repo appears abandoned
- If a repository doesn't exist or can't be found, state that explicitly

## Output

Return findings in the format specified by the extraction instructions.

If no format is specified, use this default structure:

- **Repository**: URL and metadata
- **Findings**: Organized by the categories requested
- **Code snippets**: With file paths and context
- **Gaps**: What was requested but not found

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…