bjornmelin/context7-research
skills/context7-research/SKILL.md
Deep library, dependency, framework, and API documentation research using Context7 MCP tools only. Use when you need up-to-date docs, version-specific API reference, migration guidance, or to verify code against official documentation. Triggers on requests like “look up docs”, “API reference”, “how do I use X”, “latest/current”, “deprecated”, “breaking changes”, “best practices”, or whenever correctness depends on primary documentation.
$ install --global
skillsauthnpx skillsauth add bjornmelin/dev-skills context7-researchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 11, 2026, 3:44 AM138.8s7 files scanned
SKILL.md
- name:
- context7-research
- description:
- Deep library, dependency, framework, and API documentation research using Context7 MCP tools only. Use when you need up-to-date docs, version-specific API reference, migration guidance, or to verify code against official documentation. Triggers on requests like “look up docs”, “API reference”, “how do I use X”, “latest/current”, “deprecated”, “breaking changes”, “best practices”, or whenever correctness depends on primary documentation.
Context7 Research
Use Context7 as the source of truth for library/framework documentation during implementation, reviews, and debugging.
Workflow (MUST FOLLOW)
- Extract:
libraryName: product/package/framework name (e.g.,next.js,zod,supabase)objective: what you need to do (e.g., “configure SSR auth”, “migrate v3->v4”, “use hook X”)version: only if the user specifies one or you can infer it from repo context (otherwise default to “latest”).
- If the user already provided a Context7 library ID in
/org/project(or/org/project/version) format, skip resolution. - Otherwise call
mcp__context7__resolve-library-idwith:libraryName: extracted namequery: the full user objective (not just a keyword)
- Select the best match using this rubric:
- Exact/closest name match
- Highest source reputation
- Highest snippet coverage (prefer more snippets when reputation is similar)
- Highest benchmark score
- Versions available that match the requested version (if any)
- Call
mcp__context7__query-docswith the selectedlibraryIdand a tight query (see Query Budget). - Synthesize an answer:
- Include the
libraryIdused (and version if applicable) - Quote or paraphrase only what’s needed; prefer code examples
- If docs are missing/ambiguous, label the gap as
UNVERIFIEDand ask for the smallest clarification needed.
- Include the
Query Budget (HARD LIMIT)
Use at most 3 mcp__context7__query-docs calls per user request. Plan the queries up-front:
- Query 1 (overview): “Explain the concept and where it lives in the docs; include minimal example.”
- Query 2 (API details): “Exact function/class/method signatures and usage examples for the user’s task.”
- Query 3 (edge cases): “Pitfalls, errors, version differences, and recommended patterns.”
If you can’t cover everything within 3 calls, ask the user to narrow scope (or pick the highest-impact subquestion).
Output (DEFAULT SHAPE)
- Start with the recommended approach (1–5 bullets).
- Include at least one doc-backed example/snippet when the question is about code.
- End with “Assumptions / Gaps” if anything is uncertain (
UNVERIFIED) or version-dependent.
Resources
- Playbook:
references/playbook.md - Troubleshooting:
references/troubleshooting.md - Design + scoring (maintainers):
references/design-spec.md - Report template:
assets/report-template.md - Generate a new report file:
python3 scripts/new_report.py --out ./context7-research.md --library-name "<name>" --question "<objective>"
Related Skills
bjornmelin/multi-model-review
development
VerifiedTrustedCommunity
Pre-PR multi-model review, parallel opus and codex exec adversarial lanes, then adversarial verification of merged findings. Read-only. Use before shipping nontrivial diffs.
3SKILL.mdUpdated Jul 23, 2026
bjornmelin/codex-review
tools
VerifiedTrustedCommunity
Independent gpt-5.6 diff review via the Codex CLI, normal or steerable adversarial with JSON findings. Use before shipping nontrivial changes.
3SKILL.mdUpdated Jul 23, 2026
bjornmelin/codex-delegate
development
VerifiedTrustedCommunity
Delegate implementation, investigation, or bulk work to gpt-5.6 codex via pinned codex exec. Use for clear-spec builds, migrations, debugging, or any task MODELS.md routes to codex.
3SKILL.mdUpdated Jul 23, 2026
bjornmelin/pre-mortem
development
VerifiedTrustedCommunity
Adversarial pre-mortem: imagine the plan failed, work backwards to surface risky assumptions + irreversible bets, then harden them. Proactively offer it (after the current request; confirm first) before a hard-to-reverse or one-way-door call (API, schema, framework, a hire), an all-upside plan, or unvalidated assumptions. Also on request.
3SKILL.mdUpdated Jul 22, 2026