القائمة
Web research skill for augmenting agent context with current information. Used when outdated information could lead to broken implementations or wasted effort.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when developing rough ideas into designs, before writing code or implementation plans - refines concepts through collaborative questioning and incremental validation
Use when creating new skills or editing existing skills - applies prompt engineering principles to write clear, goal-focused process documentation that trusts LLM intelligence
Use when encountering bugs, test failures, or unexpected behavior - ensures root cause understanding before attempting fixes
Use when analyzing YouTube videos for research, learning, or understanding how content relates to a project - downloads transcripts with yt-dlp, chunks long content, and provides context-aware analysis
| name | research |
| description | Web research skill for augmenting agent context with current information. Used when outdated information could lead to broken implementations or wasted effort. |
Examples: "Is useEffect still the way to handle this in React 18?", "Did Stripe change their webhook payload?", "What's the current Node LTS version?"
Just search, grab the answer, keep coding. No storage, no ceremony, no permission needed.
When: The decision really matters Time: 5-15 minutesExamples: Choosing between competing technologies, understanding a new architectural pattern, debugging something that doesn't match documentation.
Always ask first: "This needs deeper research (5-15 min). Should I dig into this now?" Let the user decide if they want to pause for research or continue with existing knowledge.
Research thoroughly, save findings in research/[topic].md for team reference.
Always use the best available web search. Priority order:MCP servers (preferred when available):
Built-in tools (fallback):
Tell the user which you're using:
This transparency helps users understand tool selection and configure MCP servers if desired.
Start with official sources - docs, changelogs, GitHub releases. Then expand to community discussions if needed. Output should be scannable and actionable. Skip the fluff, get to what matters.Good pattern:
Breaking change: redirectToCheckout() removed in v4
New pattern:
Migration: [Specific code example]
Source: Stripe docs v2024.11.15
Recognize patterns: When you see version-specific errors, deprecated methods, or post-2023 technologies, that signals research is needed.Be transparent: Say "I should verify this" or "Let me check current best practices" rather than guessing.
Speed over perfection: For quick checks, first good answer wins. For deep dives, thoroughness matters.
No unnecessary storage: Quick research lives in the conversation. Only save deep research that others might reference.
Don't research everything. If your React knowledge from 2023 still works and the user isn't hitting issues, just build. Research is a tool, not a crutch.