# Research Current Library Documentation

Library guidance becomes outdated as frameworks change. This skill retrieves current documentation through Context7 during AI coding conversations.

## Install

```bash
npx skillstore add sickn33/context7-auto-research
```

## Metadata

- Status: approved
- Slug: sickn33-context7-auto-research
- Skillstore revision: r2
- Version status: missing
- Tree hash: fa9039d887dd25cd414539a00e4a0183b8b1a53ae4440c40a4c1f6e67a389a02
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/context7-auto-research
- Ref: f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-context7-auto-research
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-context7-auto-research/manifest

## Capabilities

- Fetches current library and framework documentation through the Context7 API.
- Supports research requests about React, Next.js, Prisma, and other popular libraries.
- Works through natural requests in Claude, Codex, and Claude Code conversations.
- Supports optional API key configuration for higher rate limits.
- Can activate automatically when a conversation requires library documentation.

## Use Cases

- Check Framework Changes: Retrieve current framework documentation before updating an application or adopting a changed API.
- Verify Library Guidance: Confirm current library behavior while reviewing implementation plans, examples, or technical recommendations.
- Prepare Accurate Tutorials: Research current documentation before writing lessons, migration notes, or internal developer guides.

## Prompt Templates

### Find Current Documentation

```
Find the latest documentation for [library] about [feature]. Summarize the recommended approach and identify any version requirements.
```

### Compare Framework Versions

```
Research how [feature] differs between [framework version A] and [framework version B]. Cite the relevant documentation and summarize migration concerns.
```

### Validate an Implementation Plan

```
Check current [library] documentation against this implementation plan: [plan]. Identify unsupported assumptions, required configuration, and recommended changes.
```

### Research a Multi-Library Integration

```
Research the current documentation for [library A], [library B], and [framework]. Explain integration constraints, version compatibility, and unresolved questions.
```

## Limitations

- Coverage and freshness depend on documentation available through Context7.
- Higher request volumes may require an API key.
- The skill does not replace testing against the target project and environment.
- Ambiguous library names or versions may require clarification.

## Best Practices

- Specify the library, version, and feature whenever possible.
- Configure an API key through environment variables when higher rate limits are required.
- Verify recommendations in the target project before changing production code.

## Anti Patterns

- Do not request broad research without naming the relevant library or framework.
- Do not assume documentation examples match every project configuration.
- Do not treat retrieved guidance as a substitute for testing or expert review.

## Security Audit

- Audited at: 2026-07-23T21:25:04.511\+00:00
- Summary: Both static findings are false positives. One is a fenced installation example, and the other is a Markdown repository link; neither executes automatically. No prompt injection or malicious intent appears in SKILL.md.

## Stats

- Views: 115
- Downloads: 17
- Favorites: 0
- Popularity score: 0