Notre avis
Effectue des recherches web, consulte de la documentation et évalue des technologies pour fournir des informations externes au codebase.
Points forts
- Accès rapide à des informations à jour via le web
- Synthèse organisée avec sources et justifications
- Sauvegarde des recherches pour référence future
- Couvre plusieurs types de besoins (doc API, comparaisons, résolution de bugs)
Limites
- Nécessite un accès web et des outils de recherche
- Peut fournir des informations obsolètes si les sources ne sont pas vérifiées
- Ne remplace pas l'exploration directe du codebase
Lorsque vous avez besoin d'informations provenant de sources externes (documentations, articles, forums) pour prendre une décision ou résoudre un problème.
Lorsque l'information recherchée se trouve dans le codebase existant (utilisez plutôt l'exploration de code).
Analyse de sécurité
SûrThe 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.
Aucun point d'attention détecté
Exemples
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.
Priorisation de Tâches
Productivite
Priorise vos tâches avec les frameworks Eisenhower, ICE et RICE.
Generateur de Rapport Hebdomadaire
Productivite
Generez des rapports de statut hebdomadaires structures et concis.
Rapport de Daily Standup
Productivite
Génère des rapports de daily standup structurés et concis.