Agent skill
research-methodology
Structured research using sophisticated query design, source vetting, and synthesis techniques. Use when conducting competitive analysis, market scans, historical investigations, or trend research.
Install this agent skill to your Project
npx add-skill https://github.com/NickCrew/Claude-Cortex/tree/main/skills/research-methodology
SKILL.md
Research Methodology
Structured approach to finding, vetting, and synthesizing information from diverse sources. Turns research questions into trustworthy, actionable findings through systematic query design, source evaluation, and cross-referencing.
When to Use This Skill
- Conducting competitive analysis or market scans
- Investigating historical events, trends, or technical evolution
- Fact-checking claims across multiple sources
- Synthesizing research into structured deliverables (reports, tables, timelines)
- Any research task that requires more than a single search query
Quick Reference
| Resource | Purpose | Load when |
|---|---|---|
references/search-strategies.md |
Query design, source vetting, fact verification, synthesis techniques | Starting any research task |
Workflow
Phase 1: Scope → Define research objective, key questions, constraints
Phase 2: Explore → Design queries, search broadly, capture sources
Phase 3: Verify → Vet sources, cross-reference claims, assess credibility
Phase 4: Synthesize → Organize findings into structured deliverables
Phase 1: Scope the Research
Before searching, clarify the research objective:
- State the question -- what exactly are we trying to learn?
- Define success criteria -- what does a complete answer look like?
- Set constraints -- time period, geography, domains, source types
- List hypotheses -- what do we expect to find? (helps detect bias)
- Identify key terms -- domain vocabulary, synonyms, related concepts
Scoping Template
**Research Question**: [precise question]
**Success Criteria**: [what constitutes a complete answer]
**Constraints**: [time period, scope, source types]
**Key Terms**: [domain vocabulary and synonyms]
**Initial Hypotheses**: [what we expect, to check against later]
Phase 2: Explore
Design multiple query variations and search broadly before narrowing:
- Create 3-5 query variations per research question
- Search broadly first -- cast a wide net with general terms
- Refine iteratively -- narrow based on initial results
- Track what you searched -- record every query for reproducibility
Query Design Principles
- Use exact-match phrases in quotes for precision
- Exclude noise with negative keywords
- Target specific timeframes for recency or historical depth
- Vary terminology across queries to avoid vocabulary bias
- Use domain-specific operators when available (site:, filetype:, etc.)
Source Capture
For each promising source, record:
- URL and access date
- Key claims with direct quotes
- Author/publisher and their domain authority
- Any noted biases or limitations
Phase 3: Verify
Vet sources and cross-reference claims before trusting them:
- Assess source authority -- who wrote it, what are their credentials?
- Check recency -- is the information current enough for the question?
- Detect bias -- does the source have a commercial, political, or ideological interest?
- Triangulate -- require 2+ independent sources for any key claim
- Seek primary sources -- follow citation chains to the original data
Confidence Rating
| Level | Criteria |
|---|---|
| Confirmed | 3+ independent, authoritative sources agree |
| Likely | 2 sources agree, no contradictions found |
| Uncertain | Single source or sources disagree |
| Contested | Credible sources directly contradict each other |
Phase 4: Synthesize
Organize findings into a structured deliverable:
Standard Research Report Structure
## Research Summary
[1-2 paragraph overview of findings]
## Key Findings
- [Finding 1] — [confidence level]
- [Finding 2] — [confidence level]
## Detailed Analysis
[Organized by theme or question]
## Source Credibility Assessment
| Source | Authority | Recency | Bias Risk | Rating |
|--------|-----------|---------|-----------|--------|
## Gaps and Limitations
[What we couldn't determine and why]
## Recommendations
[Next steps or actions based on findings]
Anti-Patterns
- Do not rely on a single source for any key claim
- Do not present uncertain findings as confirmed facts
- Do not skip source vetting for convenience
- Do not omit contradictory evidence -- always surface disagreements
- Do not let initial hypotheses bias which findings you report
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
claude-consult
Consult Claude specialist agents during implementation for codebase understanding, pattern checking, security review, debugging help, and more. Use this skill whenever you're unsure about conventions, stuck on a failure, or need expert input before writing code. Does not replace the formal review gates in agent-loops — this is for mid-implementation consultation.
doc-quality-review
Assess documentation quality across readability, consistency, audience fit, and prose clarity. Produces a scored review with actionable findings. This skill should be used before releases, during doc reviews, or when documentation feels unclear or inconsistent.
event-driven-architecture
Event-driven architecture patterns with event sourcing, CQRS, and message-driven communication. Use when designing distributed systems, microservices communication, or systems requiring eventual consistency and scalability.
prompt-engineering
Optimize prompts for LLMs and AI systems with structured techniques, evaluation patterns, and synthetic test data generation. Use when building AI features, improving agent performance, or crafting system prompts.
compliance-audit
Regulatory compliance auditing across GDPR, HIPAA, PCI DSS, SOC 2, and ISO frameworks with automated evidence collection and gap analysis. Use when conducting compliance assessments, preparing for certifications, or implementing regulatory controls.
react-performance-optimization
React performance optimization patterns using memoization, code splitting, and efficient rendering strategies. Use when optimizing slow React applications, reducing bundle size, or improving user experience with large datasets.
Didn't find tool you were looking for?