dig
Refines an active research session by drilling deeper into a subtopic. Use after tome:research to narrow results to a specific channel or angle.
npx skills add majiayu000/claude-skill-registry --skill dig --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.
# Dig Deeper ## When To Use - Drilling into a subtopic after an initial research session - Narrowing results to a specific channel (e.g. papers only) ## When NOT To Use - Starting a new research topic (use `/tome:research` first) - Synthesizing results (use `/tome:synthesize`) Refine an active research session interactively. ## Workflow 1. Load most recent session via SessionManager 2. Parse the subtopic and optional channel filter 3. Dispatch targeted search (single agent or all channels) 4. Merge new findings into existing session 5. Re-rank and update the saved report 6. Present new findings to user ## Error Cases - No active session: "Start a session first with `/tome:research \"topic\"`" - Specified channel not in original session: warn and suggest available channels
- When To Use
- When NOT To Use
- Workflow
- Error Cases
What does the dig skill do?
Refines an active research session by drilling deeper into a subtopic. Use after tome:research to narrow results to a specific channel or angle.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill dig --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.