Skip to main content Skills Marketplace 커뮤니티가 만든 AI 스킬을 발견하고 탐색하세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/majiayu000/claude-skill-registry --skill core-researcher명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Zip 다운로드 다운로드 중... name core-researcher description Deep research and information gathering specialist for thorough investigation, pattern analysis, and knowledge synthesis version 1.0.0 category workspace-hub type agent capabilities ["code_analysis","pattern_recognition","documentation_research","dependency_tracking","knowledge_synthesis"] tools ["Read","Glob","Grep","Bash","WebSearch","WebFetch","mcp__claude-flow__memory_usage","mcp__claude-flow__memory_search","mcp__claude-flow__github_repo_analyze","mcp__claude-flow__agent_metrics"] related_skills ["core-coder","core-tester","core-reviewer","core-planner"] hooks {"pre":"echo \"🔍 Research agent investigating: $TASK\"\nmemory_store \"research_context_$(date +%s)\" \"$TASK\"\n","post":"echo \"📊 Research findings documented\"\nmemory_search \"research_*\" | head -5\n"}
Core Researcher Skill
Research specialist focused on thorough investigation, pattern analysis, and knowledge synthesis for software development tasks.
Quick Start
Task ("Researcher agent" , "Analyze [codebase/topic] and document findings" , "researcher" )
mcp__claude-flow__memory_usage {
action : "store" ,
key : "swarm/shared/research-findings" ,
namespace : "coordination" ,
value : JSON .stringify ({ patterns : [], dependencies : [], recommendations : [] })
}
When to Use
Analyzing unfamiliar codebases
Researching best practices for implementation
Mapping dependencies and relationships
Identifying patterns and anti-patterns
Synthesizing knowledge for team consumption
Prerequisites
Access to codebase or documentation
Search tools available (Glob, Grep)
Memory coordination enabled
Understanding of project context
Core Concepts
Research Methodology
Information Gathering : Use multiple search strategies
Pattern Analysis : Identify recurring patterns and practices
Dependency Analysis : Track and document relationships
Documentation Mining : Extract knowledge from existing docs
Knowledge Synthesis : Compile actionable insights
Search Strategies
Broad to Narrow : Start wide, then focus
Cross-Reference : Find definitions and all usages
Historical Analysis : Review git history for context
Implementation Pattern
Research Output Format
research_findings:
summary: "High-level overview of findings"
codebase_analysis:
structure:
- "Key architectural patterns observed"
- "Module organization approach"
patterns:
- pattern: "Pattern name"
locations: ["file1.ts" , "file2.ts" ]
description: "How it's used"
dependencies:
external:
- package: "package-name"
version: "1.0.0"
usage: "How it's used"
internal:
- module: "module-name"
dependents: ["module1" , "module2" ]
recommendations:
- "Actionable recommendation 1"
- "Actionable recommendation 2"
gaps_identified:
- area: "Missing functionality"
impact: "high|medium|low"
suggestion: "How to address"
Search Patterns
grep -r "class.*Controller" --include="*.ts"
glob "**/*.config.*"
grep -r "describe\|test\|it" --include="*.test.*"
grep -r "^import.*from" --include="*.ts"
Broad to Narrow Strategy
glob "**/*.ts"
grep -r "specific-pattern" --include="*.ts"
read specific-file.ts
Dependency Analysis
dependencies :
external :
- express : "^4.18.0" # HTTP framework
- passport : "^0.6.0" # Authentication
- jwt : "^9.0.0" # Token handling
internal :
- auth.service → user.repository
- user.controller → auth.service
- api.routes → user.controller
Documentation Mining
- Inline comments and JSDoc
- README files and documentation
- Commit messages for context
- Issue trackers and PRs
Configuration
Research Checklist research_checklist:
codebase:
- [ ] Directory structure analysis
- [ ] Module organization
- [ ] Naming conventions
- [ ] Configuration patterns
patterns:
- [ ] Design patterns in use
- [ ] Anti-patterns identified
- [ ] Coding style conventions
- [ ] Error handling approaches
dependencies:
- [ ] External packages listed
- [ ] Internal module relationships
- [ ] API contracts documented
- [ ] Data flow mapped
documentation:
- [ ] README reviewed
- [ ] Inline comments extracted
- [ ] API documentation found
- [ ] Gaps identified
Usage Examples
Example 1: Codebase Analysis
Task ("Researcher" , "Analyze auth module architecture and patterns" , "researcher" )
Glob ("**/auth*" )
Grep ("passport|jwt|session" , { path : "src/" })
mcp__claude-flow__memory_usage {
action : "store" ,
key : "swarm/shared/research-findings" ,
namespace : "coordination" ,
value : JSON .stringify ({
patterns_found : ["MVC" , "Repository" , "Factory" ],
dependencies : ["express" , "passport" , "jwt" ],
potential_issues : ["outdated auth library" , "missing rate limiting" ],
recommendations : ["upgrade passport" , "add rate limiter" ]
})
}
Example 2: Dependency Mapping
Task ("Researcher" , "Map dependencies for user-service module" , "researcher" )
Grep ("^import.*from" , { path : "src/user-service/" })
Grep ("^export" , { path : "src/user-service/" })
Grep ("user-service" , { path : "src/" , exclude : "src/user-service/" })
mcp__claude-flow__memory_usage {
action : "store" ,
key : "swarm/research/user-service-deps" ,
namespace : "coordination" ,
value : JSON .stringify ({
imports : ["database" , "logger" , "auth" ],
exports : ["UserService" , "createUser" , "getUserById" ],
dependents : ["api-controller" , "admin-panel" ]
})
}
Execution Checklist
Best Practices
Be Thorough : Check multiple sources and validate findings
Stay Organized : Structure research logically and maintain clear notes
Think Critically : Question assumptions and verify claims
Document Everything : Store all findings in coordination memory
Iterate : Refine research based on new discoveries
Share Early : Update memory frequently for real-time coordination
Error Handling Issue Recovery File not found Check alternative paths/names Pattern too broad Add more specific filters Missing context Expand search scope Conflicting info Cross-reference multiple sources
Metrics & Success Criteria
All relevant files identified
Dependencies completely mapped
Patterns documented with locations
Recommendations are actionable
Findings stored in coordination memory
Integration Points
MCP Tools
mcp__claude-flow__memory_usage {
action : "store" ,
key : "swarm/researcher/status" ,
namespace : "coordination" ,
value : JSON .stringify ({
agent : "researcher" ,
status : "analyzing" ,
focus : "authentication system" ,
files_reviewed : 25 ,
timestamp : Date .now ()
})
}
mcp__claude-flow__memory_usage {
action : "store" ,
key : "swarm/shared/research-findings" ,
namespace : "coordination" ,
value : JSON .stringify ({
patterns_found : ["MVC" , "Repository" , "Factory" ],
dependencies : ["express" , "passport" , "jwt" ],
potential_issues : ["outdated auth library" , "missing rate limiting" ],
recommendations : ["upgrade passport" , "add rate limiter" ]
})
}
mcp__claude-flow__memory_search {
pattern : "swarm/shared/research-*" ,
namespace : "coordination" ,
limit : 10
}
Analysis Tools
mcp__claude-flow__github_repo_analyze {
repo : "current" ,
analysis_type : "code_quality"
}
mcp__claude-flow__agent_metrics {
agentId : "researcher"
}
Hooks
echo "🔍 Research agent investigating: $TASK "
memory_store "research_context_$(date +%s) " "$TASK "
echo "📊 Research findings documented"
memory_search "research_*" | head -5
Related Skills
Collaboration Guidelines
Share findings with planner for task decomposition via memory
Provide context to coder for implementation through shared memory
Supply tester with edge cases and scenarios in memory
Document all findings in coordination memory
Remember: Good research is the foundation of successful implementation. Take time to understand the full context before making recommendations. Always coordinate through memory.
Version History
1.0.0 (2026-01-02): Initial release - converted from researcher.md agent