fetch-library-docs

You can fetch official library documentation with token-efficient content-type filtering. By specifying content types like examples or api-ref, the skill filters out irrelevant content to achieve 60-90% token savings when retrieving React or Next.js docs.

Content-type filtering reduces token usage by extracting only specific documentation sections needed, such as setup, concepts, migration, or api-ref. This targeted extraction prevents loading entire documentation files, achieving 60-90% token savings for API reference lookups.

Yes, you can look up Prisma or FastAPI documentation using only the library name. The skill automatically resolves library names to Context7-compatible IDs, mapping the provided name to fetch targeted guidance without requiring a specific library ID.

The best way to find troubleshooting and migration guides is to use flexible content-type extraction. You can request specific content types like troubleshooting, migration, or patterns to surface targeted guidance for debugging errors and upgrading between library versions.

Yes, you need python3 and jq installed as dependencies to run the scripts that fetch and filter official framework documentation. These tools process the content-type filtering logic required for token-efficient retrieval.

You should use content-type filtering instead of fetching all documentation when you need specific information like API usage, setup instructions, or best practices for coding tasks. Fetching all should be reserved for comprehensive library reviews, as it consumes significantly more tokens.