index-lib-docs

Generate a project-libs documentation skill from package manifests across Node.js, Python, Rust, and Go.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/884js/agent-skills --skill index-lib-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: index-lib-docs
Source: https://github.com/884js/agent-skills/tree/main/skills/index-lib-docs
Command: npx skills add https://github.com/884js/agent-skills --skill index-lib-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a reusable, self-contained skill (project-libs) that documents all project dependencies by discovering libraries, their versions, and appropriate documentation resources, so users can quickly browse and reference library docs.

Core Features & Use Cases

  • Automatically detects dependencies from common manifests across multiple ecosystems (npm, pyproject.toml, Cargo.toml, go.mod) and prepares per-library references.
  • Produces a dedicated .claude/skills/project-libs structure containing a main SKILL.md and per-library reference files.
  • Supports downstream usage by triggering on library imports, and by offering direct reference navigation for questions about those libraries.

Quick Start

Run the auto-lib-docs process to generate the project-libs skill and references for the current project.

Frequently Asked Questions about index-lib-docs

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

FAQPage Schema
How do I auto-generate documentation for project dependencies across multiple languages?

You can auto-generate documentation for project dependencies by scanning package manifests like package.json, pyproject.toml, Cargo.toml, and go.mod to discover libraries and collect their docs into a structured reference.

What's the best way to create a centralized reference for all my Node.js and Python library docs?

Creating a centralized reference involves scanning dependency manifests to locate each library, discovering documentation URLs via registries or web search, and aggregating per-library references into a single navigable skill file.

Does dependency documentation generation work for Rust and Go projects?

Yes, dependency documentation generation works for Rust and Go projects by locating and parsing their respective package manifests (Cargo.toml and go.mod) to identify libraries and retrieve their documentation.

How do I set up a skill that triggers automatically when I import libraries in my project?

To trigger a skill automatically on library imports, generate a dedicated configuration that includes trigger settings alongside aggregated documentation, so the reference activates whenever relevant dependencies are imported.

How are documentation URLs discovered for dependencies that are not listed in standard registries?

Documentation URLs for unlisted dependencies are discovered by performing web searches and checking for standard documentation files like llms.txt, ensuring accurate references even when registry data is incomplete.