Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/HezaoHezao/poirot --skill deep-research명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | deep-research |
| description | Systematic multi-angle web research methodology. |
| allowed-tools | ["web_search","browse_page","write_file"] |
| enabled | true |
| related-skills | ["github-deep-research","consulting-analysis"] |
| license | MIT |
| author | Adapted from deer-flow (Bytedance, MIT) |
Systematic methodology for thorough web research. Load this skill BEFORE starting any content generation task to ensure information from multiple angles, depths, and sources.
Always load when:
Never generate content based solely on general knowledge. A single search query is NEVER enough.
Start with broad searches to understand the landscape:
For each important dimension identified, conduct targeted research:
browse_page to read important sources in full,
not just snippetsEnsure comprehensive coverage by seeking diverse information types:
| Information Type | Purpose | Example Searches |
|---|---|---|
| Facts & Data | Concrete evidence | "statistics", "data", "market size" |
| Examples & Cases | Real-world applications | "case study", "example", "implementation" |
| Expert Opinions | Authority perspectives | "expert analysis", "interview", "commentary" |
| Trends & Predictions | Future direction | "trends 2026", "forecast", "future of" |
| Comparisons | Context and alternatives | "vs", "comparison", "alternatives" |
| Challenges & Criticisms | Balanced view | "challenges", "limitations", "criticism" |
Before proceeding to content generation, verify:
If any answer is NO, continue researching before generating content.
# Be specific with context
"enterprise AI adoption trends 2026"
# Include authoritative source hints
"[topic] research paper"
"[topic] McKinsey report"
# Search for specific content types
"[topic] case study"
"[topic] statistics"
# Use temporal qualifiers — use the ACTUAL current year
"[topic] 2026"
"[topic] latest"
Always check the current date before forming search queries:
| User intent | Temporal precision | Example query |
|---|---|---|
| "today / just released" | Month + Day | "tech news February 28 2026" |
| "this week" | Week range | "technology releases week of Feb 24 2026" |
| "recently / latest" | Month | "AI breakthroughs February 2026" |
| "this year / trends" | Year | "software trends 2026" |
Use browse_page to read full content when:
Research is iterative:
Research is sufficient when you can confidently answer:
After completing research, you should have:
Only then proceed to content generation.