메뉴
Use when current web info needed, verifying APIs still work, checking latest versions, or avoiding outdated implementations
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | research |
| description | Use when current web info needed, verifying APIs still work, checking latest versions, or avoiding outdated implementations |
| version | 1.2.0 |
| category | research |
| triggers | ["research","look up","check current","verify API","is this still","latest version","deprecated"] |
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.Use when facing hard architectural decisions, multiple valid approaches exist, need diverse perspectives before committing, or want M-of-N synthesis on complex problems
Use when rough ideas need design before code, requirements are fuzzy, multiple approaches exist, or you need to explore options before implementation
Use when testing MCP servers, debugging MCP tool responses, exploring MCP capabilities, or diagnosing why an MCP tool returns unexpected data
Use when debugging bugs, test failures, unexpected behavior, or needing to find root cause before fixing
Use when managing project learnings - view, add, search, prune, or export operational knowledge that persists across sessions
Use when shipping code - complete workflow: merge main, run tests, multi-review with auto-fix, commit, push, create PR. Replaces manual commit-push-pr flows.
