api-learn

Collect official API documentation into structured project references.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/oozoofrog/codex-skills --skill api-learn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-learn
Source: https://github.com/oozoofrog/codex-skills/tree/main/api-learn
Command: npx skills add https://github.com/oozoofrog/codex-skills --skill api-learn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill collects official API documentation from libraries/frameworks, normalizes and stores it as CLAUDE references inside the project (.claude/references), and registers authoritative knowledge in CLAUDE.md to streamline internal learning workflows.

Core Features & Use Cases

  • Collects official API docs from vendor sites, docs repos, and tutorials for targeted libraries.
  • Normalizes content and saves structured summaries to .claude/references/{library}.md with metadata and usage notes.
  • Updates CLAUDE.md to surface API references as primary knowledge sources for project teammates.

Quick Start

Use the api-learn skill to collect the react-query documentation and save it to .claude/references/react-query.md.

Frequently Asked Questions about api-learn

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

FAQPage Schema
How do I internalize API documentation into Claude project references?

To internalize API documentation, this Skill scans your libraries, fetches official vendor docs, and stores structured summaries directly under .claude/references as markdown files. It normalizes the content so teammates can access authoritative knowledge without leaving the workspace.

Can I save official library documentation to CLAUDE.md for project context?

Yes, you can save official library documentation to CLAUDE.md. The Skill registers the collected API references as primary knowledge sources by updating CLAUDE.md, ensuring the documentation surfaces automatically for project teammates.

What is the best way to collect vendor API docs and normalize them for internal learning?

The best way to collect vendor API docs is using a skill that coordinates web search and documentation retrieval to fetch core docs, normalize the content, and save structured summaries with metadata and usage notes to your local workspace.

Do I need any dependencies or external components to fetch and store API references?

No dependencies or external components are required to fetch and store API references. The Skill operates independently to detect the library name, coordinate web search, retrieve documentation, and update reference files within your project.

How does the api-learn skill detect library names and coordinate documentation retrieval?

The api-learn skill detects the library name from your project context, then coordinates web search and documentation retrieval to fetch core docs from vendor sites, docs repos, and tutorials. It outputs structured markdown summaries to .claude/references.