research
Research and gather reliable information about libraries, APIs, specifications, and best practices. Use when you need to understand external documentation before planning or implementing a feature.
Best use case
research is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Research and gather reliable information about libraries, APIs, specifications, and best practices. Use when you need to understand external documentation before planning or implementing a feature.
Teams using research should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/research/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How research Compares
| Feature / Agent | research | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Research and gather reliable information about libraries, APIs, specifications, and best practices. Use when you need to understand external documentation before planning or implementing a feature.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Research Research the following topic and produce a structured report: $ARGUMENTS ## Instructions 1. **Search for authoritative sources**: Use WebSearch to find official documentation, GitHub repos, and specifications 2. **Read and verify**: Use WebFetch to read documentation pages, cross-reference multiple sources 3. **Check local context**: Use Grep and Read to understand how the topic relates to the current codebase 4. **Produce a structured report** with findings, sources, and actionable recommendations ## Output Format ```text ## Research Report: [Topic] ### Summary [2-3 sentence overview] ### Key Findings 1. **[Finding]** - Detail: [What was learned] - Source: [URL] - Relevance: [How this applies to our project] ### Recommendations - [Actionable items based on findings] ### Sources - [URL]: [Description] ``` ## Rules - Always include source URLs for every claim - Prefer official documentation over blog posts - Check that documentation matches the library versions in our project - Note any uncertainties or conflicting information - Focus on what's relevant — skip tangential details
Related Skills
write-tests
Write unit tests, integration tests, or E2E tests for code. Use after implementing a feature or when test coverage is needed.
write-requirements
Write user stories, acceptance criteria, and technical requirements for a feature or change. Use when defining what needs to be built.
security-audit
Perform a security audit of the codebase. Checks for OWASP Top 10, AI-specific vulnerabilities, dependency issues, and configuration problems.
review-code
Review code changes for quality, security, and adherence to project conventions. Use after making code changes or when reviewing a pull request.
plan-task
Create a structured implementation plan for a feature, refactoring, or multi-step task. Use as the first step in the pipeline before /orchestrate. Produces a plan that the orchestrator can turn into a delegation plan.
orchestrate
Produce a structured delegation plan for parallel agent execution. Takes a task description or plan output, analyzes dependencies, assigns agents, and groups tasks for parallel execution. Use after /plan-task or when you need to plan how to delegate work across agents.
implement-feature
Implement a feature or fix a bug following the project's TypeScript patterns and conventions. Use when code changes are needed.
design-component
Design a UI component with specifications for layout, states, interactions, and accessibility. Use when creating new Vue.js components or redesigning existing ones.
deploy
Deploy the application or manage infrastructure. Handles Docker builds, CI/CD, and deployment workflows.
compliance-check
Check license compatibility, data privacy compliance, and AI ethics. Use when adding dependencies, handling user data, or reviewing regulatory requirements.
bump-dependencies
Bump or upgrade declared dependency versions in this pnpm workspace (root and packages/* package.json), with supply-chain checks before and after install. Use when the user asks to upgrade, bump, or refresh npm dependencies in manifests—not only the lockfile.
market-research
Conduct market research, competitive analysis, investor due diligence, and industry intelligence with source attribution and decision-oriented summaries. Use when the user wants market sizing, competitor comparisons, fund research, technology scans, or research that informs business decisions.