librarian

Locate official documentation and source-code evidence for npm, pip, and cargo libraries.

10|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/Lee-SiHyeon/oh-my-copilot --skill librarian-lee-sihyeon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: librarian
Source: https://github.com/Lee-SiHyeon/oh-my-copilot/tree/main/.github/skills/librarian
Command: npx skills add https://github.com/Lee-SiHyeon/oh-my-copilot --skill librarian-lee-sihyeon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The librarian Skill helps you answer questions about unfamiliar libraries by locating evidence in official documentation and real implementation examples, so you stop relying on guesses and outdated blog advice.

Core Features & Use Cases

  • Evidence-first research: Produces claims backed by GitHub permalinks to specific lines of code.
  • Doc discovery workflow: Finds official documentation via web search and sitemap-based navigation, then targets relevant pages.
  • Multiple request types: Handles conceptual “how to use” questions, implementation “show me source” requests, context like “why was this changed,” and comprehensive investigations.

Quick Start

Ask the librarian Skill to explain how to use a specific library feature and include permalinks to the exact source code and official documentation pages that support the explanation.

Frequently Asked Questions about librarian

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

FAQPage Schema
How do I find implementation examples for an unfamiliar npm dependency?

To find implementation examples for an unfamiliar npm dependency, the Skill clones open-source repositories and provides permalink line references to real source code, supporting every code claim with direct evidence.

What is the best way to look up best-practices for external libraries using GitHub?

The best way to look up best-practices for external libraries using GitHub is by classifying request intent first, then discovering official documentation and locating real implementation evidence via repository permalinks to ensure evidence-backed answering.

How does source-level investigation work for dependency debugging?

Source-level investigation for dependency debugging works by discovering official documentation and locating real implementation evidence in open-source repositories, using cloned code plus permalink line references to support every claim.

Can I use this for behavior explanations and code permalinks in open-source research?

Yes, you can use this for behavior explanations and code permalinks in open-source research. It classifies request intent to handle context queries and comprehensive investigations, supplying permalink line references to support code claims.

Does documentation discovery support web search and sitemap navigation for official docs?

Yes, documentation discovery supports web search and sitemap navigation for official docs. It finds official documentation via web search and sitemap-based navigation, then targets relevant pages to resolve questions about external libraries.

Why should I use evidence-first research instead of blog advice for unfamiliar codebases?

You should use evidence-first research instead of blog advice for unfamiliar codebases because it produces claims backed by GitHub permalinks to specific lines of code, eliminating reliance on guesses and outdated advice.