ReddRadar
Agent skill
c7
Fetches up-to-date library documentation from Context7 and saves to /tmp/context7/. Use when needing current API docs, code examples, library references, SDK documentation, or checking latest library versions. Triggers: context7, c7, library docs, fetch docs, current documentation, api reference.
Install this agent skill to your Project
npx add-skill https://github.com/antoniocascais/claude-code-toolkit/tree/main/skills/c7
SKILL.md
c7 - Context7 Documentation Fetcher
Fetch-only skill. Does NOT read docs into context.
Usage
Fetch documentation
scripts/c7.sh <library-name> "<query>"
Example:
scripts/c7.sh nextjs "app router middleware"
List cached docs
scripts/c7.sh --list
Force re-fetch (bypass cache)
scripts/c7.sh --force <library-name> "<query>"
Workflow
-
Run
scripts/c7.sh <library> "<query>" -
Handle output:
CACHED: <path> (Xh old)→ Use AskUserQuestion: "Documentation for X is already cached (Y hours old). Use cached version or fetch fresh?"- If re-fetch → run with
--force - If use cached → inform user of location, done
- If re-fetch → run with
- Success (path printed) → inform user: "Documentation saved to "
NOT_FOUND:→ Use AskUserQuestion: "Library not found in Context7. How should I proceed?" with options like retry with different name, skip, etc.RATE_LIMITED:→ inform user rate limit hit, stopAPI_ERROR:→ inform user of error, stop
-
Done. Do NOT read the file into context.
Exit Codes
| Code | Output | Action |
|---|---|---|
| 0 | filepath | Success - report location |
| 0 | CACHED: path | Ask user: use cache or re-fetch? |
| 1 | NOT_FOUND: | Ask user for alternatives |
| 2 | RATE_LIMITED: | Inform user, stop |
| 3 | API_ERROR: | Inform user, stop |
| 4 | FUZZY_MATCH: | Ask user: "Context7 matched X instead of Y. Use this or try different name?" |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
antoniocascais/claude-code-toolkit
test-quality
Guides strong, effective unit test generation using proven testing techniques. Use when writing unit tests, reviewing test quality, improving existing tests, generating test cases, checking test coverage strength, or when tests exist but may be weak. Triggers on: unit test, test quality, test coverage, write tests, improve tests, review tests, test strength, mutation testing, boundary testing.
antoniocascais/claude-code-toolkit
skill-forge
Creates new Claude Code skills with proper structure and best practices. Use when user wants to create a skill, update an existing skill, add a new command, scaffold a workflow, define skill hooks, or asks "how do I make a skill".
antoniocascais/claude-code-toolkit
workflow-review
Reviews Claude Code sessions and proposes workflow improvements. Use when: (1) /workflow-review command, (2) "review my workflow", "how can I improve", (3) after long sessions when nudged, (4) start of session with pending review. Analyzes tool usage patterns, CLAUDE.md configuration, and compares against CC best practices. Proposes: CLAUDE.md updates, new skills, underused CC features. Saves session summaries to .claude/workflow-reviews/ for cross-session continuity.
antoniocascais/claude-code-toolkit
git-commit
Plans and executes git commits with optional TICKET_ID prefix. Analyzes staged changes, proposes optimal commit structure (single or multiple), generates descriptive messages with technical context, and executes after user approval. Use when committing code changes, creating atomic commits, or splitting large changesets.
antoniocascais/claude-code-toolkit
clarice
Conducts realistic mock interviews with detailed feedback and scoring. Use for interview prep, behavioral questions, technical interviews, STAR practice, system design interviews, or interview coaching.
antoniocascais/claude-code-toolkit
pr-review
Reviews code changes before merging. Use when reviewing PRs, checking staged changes, reviewing diffs, code review, merge readiness check, or validating changes before commit/push.
Didn't find tool you were looking for?