librarian

Explore multi-repo codebases across GitHub, npm, PyPI, and crates to map library architecture.

24|7|Updated Oct 28, 2014
One-click install
npx skills add https://github.com/ajoslin/dot --skill librarian-ajoslin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: librarian
Source: https://github.com/ajoslin/dot/tree/main/config/opencode/skills/librarian
Command: npx skills add https://github.com/ajoslin/dot --skill librarian-ajoslin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enables researchers and engineers to explore multi-repo codebases to understand library internals, architecture, and implementation differences across ecosystems.

Core Features & Use Cases

  • Deep-dive cross-repo exploration to map library APIs, patterns, and integration points across GitHub, npm, PyPI, and crates.
  • Side-by-side architecture comparisons to identify diffs, best practices, and reuse opportunities.
  • Reference-driven analysis with guided workflows and diagram-ready outputs to communicate findings.

Quick Start

Identify a target repository set and generate an architecture map across sources.

Frequently Asked Questions about librarian

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

FAQPage Schema
How do I analyze library architecture and implementation differences across multiple repositories?

Cross-repo code exploration maps library APIs and patterns across GitHub, npm, PyPI, and crates to identify implementation differences and reuse opportunities. It uses reference-driven workflows and diagram-ready outputs to communicate architectural findings.

Can I compare library internals across different package ecosystems like npm and PyPI?

Yes, cross-repo analysis supports side-by-side architecture comparisons across npm, PyPI, crates, and GitHub. This enables you to map library patterns, identify diffs, and highlight best practices across different ecosystems.

What is the best way to map integration points and APIs in a multi-repo codebase?

Deep-dive cross-repo exploration maps library APIs, patterns, and integration points by enforcing a defined workflow using tool-routing guidance and reference materials. It generates diagram-ready outputs to support architectural analysis.

Do I need any specific dependencies or tools to start exploring multi-repo codebases?

No external dependencies are required to use this Skill. You simply identify a target repository set across your desired sources and generate an architecture map to begin your cross-repo analysis.

How does reference-driven analysis help with understanding codebase architecture?

Reference-driven analysis enforces a guided workflow using tool-routing guidance and reference materials to explore multi-repo codebases. It produces diagram-ready outputs that map library internals and communicate architectural findings clearly.

When should I use cross-repo exploration instead of single-repo analysis?

Use cross-repo exploration when you need to understand library internals, architecture, and implementation differences across multiple ecosystems, rather than analyzing a single repository. It is designed for mapping integration points and comparing patterns across GitHub, npm, PyPI, and crates.