library-analyzer

Analyze GitHub repositories and produce a Markdown contribution readiness report.

19|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/hamsurang/kit --skill library-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: library-analyzer
Source: https://github.com/hamsurang/kit/tree/main/plugins/library-analyzer/skills/library-analyzer
Command: npx skills add https://github.com/hamsurang/kit --skill library-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps contributors and maintainers quickly determine whether an open-source repository is ready for outside contributions by collecting repository context, identifying contribution pathways, and producing a structured, actionable Markdown report that highlights newcomer-friendly tasks.

Core Features & Use Cases

  • Repository intake & validation: Accepts GitHub URL/shorthand or local paths, validates source mode, and extracts owner/repo for enrichment.
  • Resilient data collection: Gathers README, file tree, package manifests, CI config, and issues using deepwiki-cli, gh, or webfetch fallbacks when tooling is unavailable.
  • Parallel analysis and reporting: Launches three analysis agents (codebase, lifecycle, contribution) in parallel, assembles their outputs into a templated Markdown report, and saves it under docs/library-analysis for review.
  • Use Case: A prospective contributor can request an analysis of a GitHub project to discover good-first-issues, required setup steps, and safe extension points before opening a PR.

Quick Start

Analyze the repository at https://github.com/owner/repo for contribution readiness using the library-analyzer skill.

Frequently Asked Questions about library-analyzer

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

FAQPage Schema
How do I analyze a GitHub repository for contribution readiness?

To analyze a GitHub repository for contribution readiness, provide a GitHub URL or local path to extract README, file tree, package manifests, CI configs, and issue metadata, generating a structured Markdown report highlighting newcomer-friendly tasks.

Can I assess good first issues in an open-source project before submitting a PR?

Yes, you can assess good first issues by extracting issue metadata via gh CLI when available, evaluating newcomer-friendly tasks and safe extension points to help you decide whether to submit a PR.

Do I need deepwiki-cli to extract repository context for open-source analysis?

You need deepwiki-cli or local repo access for content extraction; the analysis uses webfetch fallbacks when deepwiki-cli is unavailable, ensuring resilient data collection of README and file tree context.

What does a structured contribution report include for a repo analysis?

A structured contribution report includes codebase, lifecycle, and contribution sections assembled from parallel analysis agents, saving a Markdown file under docs/library-analysis that highlights setup steps and extension points.

How to find safe extension points in an open-source codebase?

Find safe extension points by collecting package manifests and CI configs alongside the file tree, running codebase and contribution analyses in parallel to identify areas where new contributors can safely make changes.

Does repo analysis work with local paths instead of GitHub URLs?

Yes, repo analysis works with local paths instead of GitHub URLs by validating the source mode and extracting owner/repo information, allowing you to analyze repositories directly from your filesystem.