ReddRadar
Agent skill
context7-latest-usage
Fetch the latest, docs-grounded API details and best practices for a library/framework using Context7 MCP tools `resolve-library-id` and `get-library-docs`. Use when a user asks for “最新用法/最新寫法/最佳實務/latest usage/current best practice/latest API” of a package, or asks how to implement a feature with a library and wants the newest docs-based guidance.
Install this agent skill to your Project
npx add-skill https://github.com/shaowei-g/codex-skills/tree/main/skills/context7-latest-usage
SKILL.md
Context7 Latest Usage
Workflow
1) Clarify the target library and environment
- Extract the library/framework name and ecosystem (npm/pip/cargo/go/etc).
- Extract language + runtime (e.g., Node.js 20, Python 3.12) and any required version constraints.
- Extract the user’s intent (which feature/task they want to build).
- If any of these are missing or ambiguous, ask a brief clarification question before calling Context7.
2) Resolve the library identifier (Context7)
- Call Context7 MCP tool
resolve-library-idwith the library name (and ecosystem if supported). - If multiple candidates are plausible, pick the best match and confirm with the user.
3) Fetch the newest relevant docs (Context7)
- Call Context7 MCP tool
get-library-docsfor the resolved id, scoped to the user’s task. - Prefer latest stable docs; include migration notes if the user is upgrading.
- If the docs are large, fetch only the sections needed (install, quickstart, the specific API symbols, config, and pitfalls).
4) Produce the response in a fixed format
Return exactly:
- Up-to-date API / best practices: concise bullet summary grounded in the fetched docs
- Copy-paste snippet: tailored to the user’s language/runtime/version, includes minimal setup
- Sources: Context7-provided citations/links for every important claim (especially API signatures, defaults, and behavior)
5) Failure handling (no guessing)
- If Context7 MCP tools are unavailable or any call fails, say so clearly and ask the user to enable Context7 MCP or paste/link the docs.
- Do not provide “latest API” claims without sources from Context7 output.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
shaowei-g/codex-skills
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.
shaowei-g/codex-skills
ekoen-frontend-code-review
Production-grade code review for the eKoEN frontend codebase. Use when asked to review, audit, inspect, or harden eKoEN React/Next.js frontend code, pages, components, hooks, API clients, or state layers for bugs, performance bottlenecks, TypeScript safety issues, request inefficiency, state-management risks, memory leaks, rendering regressions, error-handling gaps, duplication, or maintainability problems, especially when a structured severity-ranked report with code locations, root causes, suggested fixes, and example refactors is required.
shaowei-g/codex-skills
ekoen-backend.doc.route-error
Add HttpErrorRes responses to eKoEN backend routes when controllers can throw errors from app/util/errors/index.ts
shaowei-g/codex-skills
conventional-commit-helper
Generate and validate Conventional Commit messages for semantic-release workflows. Use when a user asks to write a commit message, asks to commit changes, asks for commit type/scope selection, or asks to enforce Conventional Commits consistency.
shaowei-g/codex-skills
codex-cli-subagent-transport
Use only when native subagent execution is unavailable and the caller needs one deterministic Codex CLI run with repo-local artifacts and a manifest-based result contract.
shaowei-g/codex-skills
skill-usage-logger
All skill MUST use this logger to record usage events in NDJSON format.Log Codex skill usage events to NDJSON with safe concurrent appends.
Didn't find tool you were looking for?