Repo Scanner

Analyze GitHub repositories to generate a structured catalog with statuses and descriptions.

17|1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/aaronjmars/miroshark-aeon --skill repo-scanner-aaronjmars
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Repo Scanner
Source: https://github.com/aaronjmars/miroshark-aeon/tree/main/skills/repo-scanner
Command: npx skills add https://github.com/aaronjmars/miroshark-aeon --skill repo-scanner-aaronjmars

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of discovering, profiling, and categorizing multiple GitHub repositories, enabling efficient management and review.

Core Features & Use Cases

  • Repository Discovery: Fetches repositories for a user or organization, filtering out archived projects.
  • Quick Profiling: Clones repositories to analyze README content, code structure, open issues, pull requests, and recent activity.
  • Assessment & Categorization: Classifies repositories into active, maintained, stale, or forks based on recent activity.
  • Documentation & Indexing: Generates a structured catalog with detailed repo data, linking repositories for project tracking and improvement opportunities.

Quick Start

Provide a GitHub username or org in the configuration, then run the skill to generate a comprehensive catalog of repositories with insights and suggested improvements.

Frequently Asked Questions about Repo Scanner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically catalog and assess multiple GitHub repositories?

To catalog and assess GitHub repositories, this skill clones repositories, reads README files, and queries issues and pull requests via CLI tools to compile structured profiles with statuses, descriptions, and enhancement opportunities.

What is the best way to profile GitHub repositories for project oversight?

Profiling GitHub repositories for project oversight involves analyzing README content, code structure, open issues, pull requests, and recent activity to classify projects as active, maintained, stale, or forks.

How do I generate a structured index of all repos for a GitHub organization?

Generating a structured index of GitHub organization repos requires fetching repositories, filtering out archived projects, and analyzing code and recent activity to output a comprehensive catalog for project tracking.

Can I track open issues and pull requests across multiple repositories at once?

You can track open issues and pull requests across multiple repositories by querying GitHub via CLI tools, which compiles the data into a comprehensive profile for ongoing project health monitoring and strategic decision-making.

Do I need to install CLI tools to analyze GitHub README files and code structure?

Analyzing GitHub README files and code structure requires CLI tools to clone repositories and query GitHub issues and pull requests, ensuring the skill can accurately assess project health and generate detailed repo profiles.

How does repository categorization based on recent activity work?

Repository categorization based on recent activity works by analyzing pull requests, issues, and updates to classify repositories into active, maintained, stale, or forks, supporting strategic decision-making and ongoing project health monitoring.