Token-efficient library documentation fetcher using Context7 MCP with 86.8% token savings through intelligent shell pipeline filtering. Fetches code examples, API references, and best practices for JavaScript, Python, Go, Rust, and other libraries.
SkillScore68Maintained
Automatic
◆Doc Ops pack
Last verified 8/21/2026
What it changes
Passed 10 of 15 test cases with the skill, and 4 of 15 without it.
Without skill27%
With skill68%
Checks it passed that the model alone missed
Executes bash scripts/fetch-docs.sh
Uses /expressjs/express as the library identifier
Uses the direct library identifier /vercel/next.js
and 5 more in the full report
9 fixed6 passed either way7 still failing0 broke
Pass-rate lift
+41 pp
Tokens
+26%
Agent turns
0%
Response time
-54%
Model gemini-3.6-flashMeasured 8/21/2026v115 of 22 cases passed with skill · 15 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
I am building a Next.js application and need page routing documentation. Please execute the documentation shell tool for Next.js routing using its fast direct identifier, and get the second page of docs.
What was checked, without and with the skill
Checked
Without skill
With skill
Uses the direct library identifier /vercel/next.js
Missed
Passed
Requests page 2 for pagination
Passed
Passed
case-03 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md196 lines10 filesincludes scripts
Context7 Efficient Documentation Fetcher
Fetch library documentation with automatic 77% token reduction via shell pipeline.
Fetch up-to-date library documentation via Context7 API. Use PROACTIVELY when:
(1) Working with ANY external library (React, Next.js, Supabase, etc.)
(2) User asks about library APIs, patterns, or best practices
(3) Implementing features that rely on third-party packages
(4) Debugging library-specific issues
(5) Need current documentation beyond training data cutoff
Always prefer this over guessing library APIs or using outdated knowledge.