research

name	research
description	Verify sources before presenting findings. Use when asked to research links or documentation.
metadata	{"last_updated":"2026-04-24","verified_against":"current local skill refresh"}

Verified Research

For choosing search, extraction, npm package, or wider tooling workflows, use ecosystem-guide.

Quick Start

1. Fetch actual source content (don't trust snippets)
2. Verify claims before presenting
3. Report failures explicitly

Tool Priority

1. GitHub repos → gh api via Bash
2. npm packages → npmx.dev API via WebFetch (see npm-package-research.md)
3. Doc pages → tavily_extract_process
4. Quick answers → ai_search (perplexity/kagi_fastgpt/exa_answer)
5. Discovery → web_search or github_search
6. Fallback → Clone repo via subagent

Core Rules

• Never present unverified findings - fetch actual content first
• Partial data ≠ success - try next tool, report failures
• No source substitution without user consent
• Flag contradictions - don't silently pick one source

References

• verification-patterns.md - Source conflicts, cutoff handling
• ai-search-providers.md - exa_answer, perplexity, kagi usage
• hallucination-prevention.md - CoVe, atomic facts
• repo-cloning-pattern.md - Subagent clone workflow
• partial-data-failures.md - Rate limits, fallbacks
• npm-package-research.md - npmx.dev type docs, version resolution, fallbacks