/research-methodology
Best practices for systematic research, source evaluation, and evidence gathering
$ npx -y skills add vstorm-co/pydantic-deepagents --skill research-methodology --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/research-methodology
Context preview
The summary Claude sees to decide when to auto-load this skill.
Best practices for systematic research, source evaluation, and evidence gathering
SKILL.md
research-methodology.SKILL.mdname: research-methodology
description: Best practices for systematic research, source evaluation, and evidence gathering
auto_load: false
Research Methodology Guide
Search Strategy
Phase 1: Broad Discovery
- Start with general queries to understand the landscape
- Use different phrasings for the same concept
- Note key terminology, authors, and organizations
Phase 2: Focused Deep-Dive
- Search for specific claims, statistics, or technical details
- Target authoritative sources identified in Phase 1
- Use exact phrases in quotes for precision
Phase 3: Verification
- Cross-reference key claims across multiple sources
- Search for counter-arguments or contradictions
- Check publication dates for recency
Source Evaluation
Reliability Hierarchy
1. **Academic papers** (peer-reviewed journals, arXiv preprints) 2. **Official documentation** (government, organization, project docs) 3. **Reputable news** (established outlets with editorial standards) 4. **Expert blog posts** (known authors with credentials) 5. **Community forums** (Stack Overflow, Reddit — use cautiously)
Evaluation Checklist
- **Authority**: Who wrote it? What are their credentials?
- **Currency**: When was it published? Is it still relevant?
- **Coverage**: Does it address the topic comprehensively?
- **Accuracy**: Can claims be verified elsewhere?
- **Objectivity**: Is there obvious bias or commercial interest?
Note-Taking Best Practices
Structure Each Note File
# [Sub-topic Title]
## Key Findings
- Finding 1 [SOURCE: url, accessed YYYY-MM-DD] [HIGH confidence]
- Finding 2 [SOURCE: url, accessed YYYY-MM-DD] [MEDIUM confidence]
## Contradictions
- Source A says X, but Source B says Y
## Gaps
- Could not find reliable data on Z
Confidence Levels
- **[HIGH]**: Multiple authoritative sources agree
- **[MEDIUM]**: Single authoritative source, or multiple less-reliable sources agree
- **[LOW]**: Single non-authoritative source, or conflicting information
Common Pitfalls
- Don't rely on a single source for important claims
- Check if "recent" articles cite outdated data
- Be wary of sources that don't cite their own sources
- Distinguish between correlation and causation
- Note when sample sizes are small or studies are preliminary
Read more
name: research-methodology description: Best practices for systematic research, source evaluation, and evidence gathering auto_load: false
Research Methodology Guide
Search Strategy
Phase 1: Broad Discovery
- Start with general queries to understand the landscape
- Use different phrasings for the same concept
- Note key terminology, authors, and organizations
Phase 2: Focused Deep-Dive
- Search for specific claims, statistics, or technical details
- Target authoritative sources identified in Phase 1
- Use exact phrases in quotes for precision
Phase 3: Verification
- Cross-reference key claims across multiple sources
- Search for counter-arguments or contradictions
- Check publication dates for recency
Source Evaluation
Reliability Hierarchy
1. **Academic papers** (peer-reviewed journals, arXiv preprints) 2. **Official documentation** (government, organization, project docs) 3. **Reputable news** (established outlets with editorial standards) 4. **Expert blog posts** (known authors with credentials) 5. **Community forums** (Stack Overflow, Reddit — use cautiously)
Evaluation Checklist
- **Authority**: Who wrote it? What are their credentials?
- **Currency**: When was it published? Is it still relevant?
- **Coverage**: Does it address the topic comprehensively?
- **Accuracy**: Can claims be verified elsewhere?
- **Objectivity**: Is there obvious bias or commercial interest?
Note-Taking Best Practices
Structure Each Note File
# [Sub-topic Title] ## Key Findings - Finding 1 [SOURCE: url, accessed YYYY-MM-DD] [HIGH confidence] - Finding 2 [SOURCE: url, accessed YYYY-MM-DD] [MEDIUM confidence] ## Contradictions - Source A says X, but Source B says Y ## Gaps - Could not find reliable data on Z
Confidence Levels
- **[HIGH]**: Multiple authoritative sources agree
- **[MEDIUM]**: Single authoritative source, or multiple less-reliable sources agree
- **[LOW]**: Single non-authoritative source, or conflicting information
Common Pitfalls
- Don't rely on a single source for important claims
- Check if "recent" articles cite outdated data
- Be wary of sources that don't cite their own sources
- Distinguish between correlation and causation
- Note when sample sizes are small or studies are preliminary
Open-source, self-hosted Claude Code - a terminal AI assistant and the Python framework behind it. Tool-calling, sandboxed execution, multi-agent teams, skills, checkpoints, unlimited context - on Pydantic AI, any model.
Repo: vstorm-co/pydantic-deepagents
Other skills on pydantic-deepagents.
- /build-and-compile
Building, compiling, and resolving dependency issues across languages
Open skill - /code-review
Systematic code review for bugs, security, style, and performance
Open skill - /data-formats
Working with diverse data formats: binary, text, structured, and custom
Open skill - /environment-discovery
Systematic exploration of unknown environments before starting work
Open skill - /git-workflow
Git operations: commits, branches, PRs, and conflict resolution
Open skill - /performant-code
Writing efficient code that handles large data and tight constraints
Open skill

