Our review
Performs web searches, documentation lookups, and technology evaluations to gather information from outside the codebase.
Strengths
- Quick access to up-to-date web information
- Organized synthesis with sources and justifications
- Saves research for future reference
- Covers various needs (API docs, comparisons, bug resolution)
Limitations
- Requires web access and search tools
- May return outdated information if sources are not verified
- Does not substitute for codebase exploration
When you need external information (docs, articles, forums) to make a decision or solve a problem.
When the needed information is within the existing codebase (use codebase exploration instead).
Security analysis
SafeThe skill uses only safe tools (WebSearch, WebFetch, Read, Write) for research purposes. It does not involve any destructive, exfiltrating, or obfuscated actions, and does not instruct execution of arbitrary code or system commands.
No concerns found
Examples
Should we use Redis or Memcached for caching?How does the Stripe webhook verification work?name: researching-topics description: > Web search, documentation lookup, and technology evaluation. Use when user says "research", "look up", "find docs", "what is", "compare options", "evaluate", or needs information from outside the codebase. Do NOT use for: codebase exploration (use exploring-codebase), implementing features (use implementing-features). compatibility: "Requires Claude Code with web access." allowed-tools: [WebSearch, WebFetch, Read, Write] metadata: author: agentic-framework version: "${VERSION}"
Researching Topics
Web search, documentation lookup, and technology evaluation.
Instructions
Step 1: Clarify the Research Question
Understand what information the user needs:
- Specific API documentation?
- Technology comparison?
- Best practices for a technique?
- Bug/error resolution?
Step 2: Search and Gather
Use web search for current information:
- Official documentation first
- Stack Overflow for common issues
- GitHub issues for library-specific problems
- Blog posts for best practices (prefer recent sources)
Step 3: Synthesize Findings
Present findings organized by relevance:
- Direct answer to the question
- Supporting evidence and sources
- Trade-offs or alternatives if applicable
- Recommended approach with justification
Step 4: Save if Valuable
If the research informs a decision, save it:
docs/research/YYYY-MM-DD-topic.md
Examples
Example 1: Technology evaluation User says: "Should we use Redis or Memcached for caching?" Steps taken:
- Search for current comparisons and benchmarks
- Check project's existing infrastructure (STACK.md)
- Compare: persistence, data structures, clustering, ease of setup Result: Recommendation with trade-offs table and links to sources.
Example 2: API documentation lookup User says: "How does the Stripe webhook verification work?" Steps taken:
- Fetch Stripe's official webhook docs
- Extract key steps: signature verification, event handling
- Provide code example matching project's language Result: Step-by-step guide with code snippet and security notes.
Troubleshooting
Outdated information found Cause: Search results may include old articles. Solution: Check publication dates. Prefer official docs. Cross-reference multiple sources.
Task Prioritizer
Productivity
Prioritizes your tasks using Eisenhower, ICE, and RICE frameworks.
Weekly Status Report Generator
Productivity
Generate structured and concise weekly status reports.
Daily Standup Report
Productivity
Generates structured and concise daily standup reports.