Documentation Lookup
Fetch current library docs via the Context7 MCP instead of training data: resolve the library ID, then query live docs and code snippets.
- What
- Fetch current library docs via the Context7 MCP instead of training data: resolve the library ID, then query live docs and code snippets.
- Cost
- Free
- Needs
- none for the installation itself — this skill is a single guidance file, no account, no API key, no payment. To use its lookups afterwards, my agent harness needs the Context7 MCP configured; that configuration is separate from this installation and I will handle it in my harness if I want the lookups.
- Level
- Beginner
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a small but high-leverage skill that stops your agent from answering library questions from stale training data. When a question depends on a framework or API, the workflow is: call the Context7 MCP's resolve-library-id to get a valid library ID (format /org/project), pick the best match by name and benchmark score, then query-docs for live documentation and code snippets. It activates for setup questions, API references, code examples, or whenever a framework name appears (React, Next.js, Prisma, Supabase, and friends). By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: requires the Context7 MCP configured in your harness (Claude Code, Cursor, Codex); without it the workflow has nothing to call; snippet quality follows the benchmark score of the matched library. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Documentation Lookup is a free Muse skill that stops your agent from answering library questions from stale training data, by fetching current library docs via the Context7 MCP instead. When a question depends on a framework or API, resolve the library ID, pick the best match by name and score, then query live docs and snippets.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: none for the installation itself — this skill is a single guidance file, no account, no API key, no payment. To use its lookups afterwards, my agent harness needs the Context7 MCP configured; that configuration is separate from this installation and I will handle it in my harness if I want the lookups. Install "Documentation Lookup" for me. When I ask about a library, framework or API, it makes my agent fetch current documentation through the Context7 MCP (its resolve-library-id and query-docs tools) instead of answering from training data. Once it is installed, I use it by asking my agent a setup, API reference or code example question about a library. Repository: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/documentation-lookup/SKILL.md Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file from the repository path into a temporary folder and look inside. It is the only file this skill needs. 2. Integrity check: Skill Harbor reviewed this listing on 2026-10-10 and recorded the fingerprint below. I want you to compute the SHA-256 of the downloaded file and compare: - SKILL.md: SHA-256 81ad2b5b4acbe02259f4b6cbfd9111d81d5cfe51025051b6048959c45f6516c1 If a fingerprint does not match, I want you to stop before installing and tell me the files changed since Skill Harbor's review, so the new version is unverified. Show me your safety findings and give me three choices: (a) wait for Skill Harbor to re-review the listing (recommended), (b) analyze the new files in detail first and then decide, (c) install anyway knowing the risk. Then wait for my answer before doing anything else. 3. Safety check: I want to see your findings explicitly, in short separate items: - every network address the code contacts (expected: none in the file itself; when the skill is used later, my questions go to the Context7 service through the MCP tools configured in my harness) - every shell command it runs (expected: none) - every place credentials, API keys or personal data are read, stored or sent (expected: none stored; the file itself tells the agent to redact secrets from any question before sending it to Context7) - any obfuscated or encoded code (expected: none, plain markdown guidance) If anything looks suspicious, stop and explain it to me before continuing. 4. Confirmation: before installing, give me a short summary of what the skill does plus your safety findings, and wait for my explicit "yes, install". 5. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "documentation-lookup". 6. Verify with no network calls: frontmatter valid, skill name is documentation-lookup, and the file is in place. 7. Report what was installed, where, and what I still need to do myself: if I want the live lookups, my agent harness needs the Context7 MCP configured — the skill itself is installed and ready either way. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.