research-lib

Compile official library documentation into markdown dossiers at .claude/docs/libraries/.

17|5|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/gaebalai/claude-code-orchestrator --skill research-lib-gaebalai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-lib
Source: https://github.com/gaebalai/claude-code-orchestrator/tree/main/.claude/skills/research-lib
Command: npx skills add https://github.com/gaebalai/claude-code-orchestrator --skill research-lib-gaebalai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the research process to gather official information, usage patterns, and constraints and convert them into complete documentation stored at .claude/docs/libraries/.

Core Features & Use Cases

  • Documentation generation: Compile official name, version, license, URL, and installation steps from multiple sources.
  • Usage and troubleshooting: Summarize core features, basic usage with code examples, and common issues.
  • Output location: Writes to the library docs path: .claude/docs/libraries/$ARGUMENTS.md.

Quick Start

Install and configure the library research prompt and instruct the AI to fetch official docs and publish a documentation draft to the target path.

Frequently Asked Questions about research-lib

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

FAQPage Schema
How do I compile official documentation for a Python library into a single file?

To compile official documentation for a Python library, aggregate official docs, READMEs, licenses, and installation commands into a publishable markdown dossier. This consolidates scattered usage information into a structured file.

What is the best way to generate a markdown dossier from web research for a programming library?

Generating a markdown dossier from web research involves aggregating official sources, release notes, and usage patterns into a structured document. It automates gathering constraints and core features into consistent markdown output.

How does automated library documentation generation handle licenses and release notes?

Automated library documentation generation handles licenses and release notes by collecting them alongside official docs and installation steps. It aggregates these official sources to produce a comprehensive markdown dossier.

Can I use web research to summarize basic usage and code examples for any programming library?

Yes, you can use web research to summarize basic usage and code examples for any programming library. The process aggregates official sources and core features to output a troubleshooting and usage guide.

Where does the generated library documentation dossier get saved?

The generated library documentation dossier is saved as a markdown file in the `.claude/docs/libraries/` directory. It outputs the compiled research based on the provided library argument.

Does automated library research work for packaging constraints and common issues?

Yes, automated library research works for packaging constraints and common issues by summarizing core features, basic usage, and troubleshooting steps. It aggregates official sources to capture these constraints during the research process.