research
Read-only external knowledge gathering via ODIN's 5-tier doc ladder (Official docs → API refs → Books/papers → Tutorials → Community). For library APIs, framework behavior, SDK migrations, version-specific docs, vendor announcements, RFCs. Verifies claims against primary sources. Invoke on \"how does X library work\", \"migration guide\", \"docs for\", or any named library/framework/SDK/API/CLI/service.
npx skills add majiayu000/claude-skill-registry --skill research-outlinedriven-odin-claude-plugin --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Research Command Read-only external knowledge gathering. Walk the 5-tier source ladder; cite every claim to a primary source; flag training-data-only assertions explicitly. Do NOT write, edit, or commit files. ## When to Apply / NOT **Apply:** - Library/framework/SDK/API docs — signatures, config options, migration - Version-specific behavior — changelogs, deprecations, breaking changes - Vendor announcements, RFCs, public web technical content - Any named library, framework, SDK, API, CLI tool, or cloud service **NOT apply:** - Questions about a local repo's code — use a codebase exploration workflow instead - Autonomous goal-directed research loops (multi-step, agent-driven) - Implementation or file editing ## Process 1. **Identify subject** — extract the library, framework, SDK, API, CLI, or topic from the user's message. Capture version if stated (e.g., `pydantic@2.7`). If version unstated, resolve latest stable at Tier 1. 2. **Resolve identifier** — look up the canonical name and version from the library's official documentation surface. If no dedicated doc tool is available, use the subject name as the search query and proceed. 3. **Walk the source ladder** — start at Tier
- When to Apply / NOT
- Process
- Source Ladder
- Required Output
- Anti-Patterns
What does the research skill do?
Read-only external knowledge gathering via ODIN's 5-tier doc ladder (Official docs → API refs → Books/papers → Tutorials → Community). For library APIs, framework behavior, SDK migrations, version-specific docs, vendor announcements, RFCs. Verifies claims against primary sources. Invoke on \"how does X library work\", \"migration guide\", \"docs for\", or any named library/framework/SDK/API/CLI/service.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill research-outlinedriven-odin-claude-plugin --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.