01
What this skill does
Use this implicitly discoverable skill when a coding decision depends on the exact API or behavior of an external library, SDK, or framework. It resolves the library and target version, establishes the supported public contract through Context7, maps GitHub evidence to the same release, and distinguishes documented usage from implementation details, tests, and historical issue or pull-request context.
02
When to use it
- 01Implementing against a current or project-pinned dependency version.
- 02Diagnosing behavior that public documentation does not fully explain.
- 03Checking API changes, regressions, bug workarounds, and release history.
- 04Verifying a recommendation against public docs, exact-ref source, and focused tests.
03
How it works
- 01
Identify the package, canonical repository, concrete question, and target version from the user or consuming project.
- 02
Resolve the Context7 library ID and query the narrow public documentation needed for that version and question.
- 03
Map the package version to an immutable GitHub tag or commit instead of silently using the default branch.
- 04
Inspect public exports, types, implementation, tests, and examples, adding releases, commits, issues, or pull requests only when needed.
- 05
Reconcile the two evidence sets and report supported usage separately from observed internals, historical context, and workarounds.
04
What you get back
- 01A direct implementation or diagnostic recommendation grounded in the supported public contract.
- 02The Context7 library ID and version plus the GitHub repository ref or commit used for verification.
- 03An explicit account of agreements, conflicts, unresolved version mappings, evidence gaps, and inferences.
05
Important boundaries
- 01Use GitHub MCP only for read-only research; implicit invocation never authorizes repository mutations.
- 02Do not silently compare versioned documentation with source from an unrelated branch or release.
- 03Do not recommend private, generated, deprecated, compatibility, test-only, or feature-flagged internals as public APIs.
- 04Do not send credentials, private source, proprietary identifiers, or personal data to Context7.
06