Lookup Documentation

lookup-docs

Look up documentation for any library using Context7. Resolves library IDs and queries versioned docs.

Marshall-Hallenbeck/dot_files·0installs5stars

SKILL.md

Full skill instructions

Lookup Documentation

Find relevant documentation for any technology using Context7 MCP.

Usage

/lookup-docs <library> <query>

Examples

/lookup-docs strapi document service populate relations
/lookup-docs mantine Modal controlled state
/lookup-docs playwright wait for network idle
/lookup-docs react server components data fetching
/lookup-docs django queryset filtering

Steps

1. Parse Input

Extract:

Library name: The technology (strapi, nextjs, mantine, django, etc.)
Query: What they want to know

2. Resolve Library ID

mcp__context7__resolve-library-id or mcp__plugin_context7_context7__resolve-library-id

Call with the library name and query for context. This returns the Context7 library ID.

3. Query Documentation

mcp__context7__query-docs or mcp__plugin_context7_context7__query-docs

Call with the resolved library ID and the specific question.

4. Synthesize Response

From the documentation results:

Extract the most relevant code examples
Identify best practices
Note any gotchas or common mistakes
Provide a clear, actionable answer

Output Format

## Documentation: [library] - [topic]

### Quick Answer
[1-2 sentence direct answer]

### Code Example
[Most relevant, complete code example]

### Key Points
- [Important detail 1]
- [Important detail 2]

### Best Practices
- [Recommended approach]
- [What to avoid]

### Source
Library: [library ID]

Install skill

Copy and run in your terminal

npx -y skills add https://github.com/Marshall-Hallenbeck/dot_files --skill lookup-docs

View on GitHub

.claude/skills/lookup-docs/SKILL.md

normalize-ai-config
Normalize agents/skills/hooks so responsibilities are separated and workflows are coherent.
0 installs
opencode-review
Run OpenCode (MiniMax) and Claude code reviews iteratively until both find no issues. Use after making changes and before committing.
0 installs
full-review
Holistic review pipeline: simplification, correctness, security, overcautious check, lint/fix, all tests, fix failures, audits, and final review. The one command that checks everything.
0 installs
multi-model-review
Run code review with 4 free OpenCode models in parallel, then have them peer-review each other to reach consensus findings.
0 installs

More skills from Marshall-Hallenbeck

Marshall-Hallenbeck/dot_files

codex-review

Run Codex and Claude code reviews iteratively until both find no issues. Use after making changes and before committing.

5 0

View

Marshall-Hallenbeck/dot_files

create-pr

Creates a pull request with proper formatting, running tests first and including a structured description.

5 0

View

Marshall-Hallenbeck/dot_files

commit

Commit session changes only, or all changes if no session edits.

5 0

View

Marshall-Hallenbeck/dot_files

run-quality-gate

Run full quality gate: linting, type checks, unit tests, and integration tests — all in parallel.

5 0

View

Marshall-Hallenbeck/dot_files

lint

Run formatting, linting, and type checking. Auto-detects project languages (Python, JS/TS, Bash). Fixes auto-fixable issues and stages changes.

5 0

View

Marshall-Hallenbeck/dot_files

Use when asked to work on, implement, or complete a GitHub issue — before writing any code, checks issue state, existing PRs, git history, and codebase to determine what work remains or if the issue is already resolved

5 0

View

Marshall-Hallenbeck/dot_files

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

5 0

View

Marshall-Hallenbeck/dot_files

fix-tests

Autonomous test-fix pipeline. Runs full suite, diagnoses each failure, fixes source code, and iterates until all tests pass. Asks the user when uncertain about intended behavior.

5 0

View