research
Trace execution paths and document how code actually behaves. Use when you need to understand how features work, walk through code flows, explain component behavior, trace where data comes from, understand relationships between components, or audit for orphaned events and dead code.
npx skills add majiayu000/claude-skill-registry --skill research-hoang604-get-thing-done --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.
<principles> ## Zero Assumption Never guess from names. `saveUser()` might delete records. READ THE CODE. ## Trust Threshold Skip deep dive the implementation ONLY if docstring documents: - What it does - What it returns - Side effects - Exceptions "Handles user data" → NOT trustworthy. Read it. ## Boundary Stop at: - Third-party libraries (assume documented behavior) - Unrelated subsystems - Full behavioral understanding ## Completeness Investigation answers: 1. What does this do, step by step? 2. What dependencies does it interact with? 3. What are inputs, outputs, side effects? 4. What errors can occur? ## No Teleportation Data doesn't appear out of nowhere. Every piece of data must have a traceable path: - **Origin:** Where was it created? - **Path:** What components touch it? - **Destination:** Where is it consumed? If data appears in component B but you can't trace it from A → investigation is **INCOMPLETE**. Corollaries: - Every WRITE needs a READER - Every READ traces back to a WRITE - Every EMIT needs a HANDLER </principles> <techniques> ## Dependency Classification | Type | Action | | -------------- | --------------------------- | | Core Logic | MUST read fully | | Infras
- Zero Assumption
- Trust Threshold
- Boundary
- Completeness
- No Teleportation
- Dependency Classification
- Data Lineage
- Before Finishing
What does the research skill do?
Trace execution paths and document how code actually behaves. Use when you need to understand how features work, walk through code flows, explain component behavior, trace where data comes from, understand relationships between components, or audit for orphaned events and dead code.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill research-hoang604-get-thing-done --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.