Research Methodology
This skill should be used when docs-researcher agent needs guidance on "how to search documentation", "WebSearch query patterns", "filtering search results", "documentation research strategy", or "creating knowledge files". Provides systematic methodology for effective technical documentation research.
What this skill does
# Research Methodology for Documentation
This skill provides systematic approach to researching technical documentation using WebSearch and WebFetch tools.
## Core Principles
1. **Validate before research** - Ensure request is specific enough
2. **Check local first** - Look in `.claude/knowledge/` before searching
3. **Official sources priority** - Start with official docs
4. **Filter aggressively** - Extract only what's relevant to context
5. **Save for reuse** - Document findings in standard format
## Request Validation
A valid research request must contain three elements:
| Element | Example | Invalid |
|---------|---------|---------|
| Technology | "React", "Effect", "Prisma" | "JavaScript library" |
| Topic | "useEffect cleanup", "pipe operator" | "how it works" |
| Context | "fixing memory leak in subscription" | "learning" |
If any element is missing, return validation error and request clarification.
## Search Strategy
### Query Formulation
Build queries progressively:
```
Level 1 (Official): {technology} official documentation {topic}
Level 2 (Tutorial): {technology} {topic} tutorial example
Level 3 (Problem): {technology} {topic} {error-message} solution
```
### Source Hierarchy
Prioritize sources in this order:
1. **Official documentation** (always check first)
- react.dev, docs.python.org, effect.website
- GitHub official repos and examples
2. **Trusted secondary sources**
- MDN Web Docs (web technologies)
- DigitalOcean Community tutorials
- Dev.to (high-quality articles only)
- Stack Overflow (accepted answers)
3. **Avoid**
- SEO-optimized content farms
- Outdated tutorials (check dates)
- AI-generated summaries
- Forums without accepted solutions
### WebSearch Patterns
Reference `references/query-patterns.md` for specific query templates per technology domain.
## Filtering Results
### Relevance Criteria
Include information that:
- Directly addresses the stated context
- Provides actionable code examples
- Explains common pitfalls for the use case
- Is current (matches stated version or latest)
Exclude information that:
- Is tangentially related
- Covers advanced edge cases not needed
- Is deprecated or version-mismatched
- Duplicates what's already found
### Extraction Process
1. Scan search results for relevance
2. Open 2-3 most promising sources
3. Extract specific sections, not entire pages
4. Verify code examples are complete
5. Note version compatibility
## Document Format
Save all knowledge files to `.claude/knowledge/` using the template in `references/document-template.md`.
### File Naming
Format: `{technology}-{topic}.md`
Examples:
- `react-useeffect-cleanup.md`
- `effect-pipe-operator.md`
- `prisma-relations.md`
- `nextauth-jwt-session.md`
Rules:
- All lowercase
- Hyphens between words
- Technology first, then topic
- No version numbers in filename
### Frontmatter Structure
Required fields in YAML frontmatter:
- `topic`: Descriptive title
- `technology`: Library/framework name
- `version`: Version researched (or "latest")
- `sources`: List of URLs used
- `created`: Date in YYYY-MM-DD format
- `context`: Original problem that triggered research
## Quality Checklist
Before saving knowledge document, verify:
- [ ] Request was properly validated
- [ ] Existing knowledge was checked first
- [ ] Official sources were consulted
- [ ] Content is specific to stated context
- [ ] Code examples are complete and tested
- [ ] Sources are cited
- [ ] File follows naming convention
- [ ] Frontmatter is complete
## Additional Resources
### Reference Files
- **`references/query-patterns.md`** - Technology-specific search query templates
- **`references/document-template.md`** - Complete knowledge document template
### Implementation Notes
This methodology is designed for Haiku model execution. Instructions are explicit and procedural to ensure consistent results across model capabilities.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.