smithery.ai

dig

Investigate bugs, features, or system behavior without making changes. Use when the user asks to investigate, debug, analyze, or understand something before editing it.

First seen Mar 21, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,159 B
  • docs SUMMARY.md 274 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

Dig

Stay in investigation mode until the user ends it. Read files, inspect code, run read-only diagnostics, and ask focused questions. Do not edit files or run write operations.

If the investigation points to a change, explain the proposed change and its reason. Ask for permission before making it. Permission covers only that specific change.

Investigation workflow

  1. Establish the question, scope, and constraints.
  2. Read the relevant files, logs, configuration, and command output.
  3. Fill evidence gaps with targeted questions or read-only checks.
  4. Separate confirmed facts from hypotheses and name the likely cause when evidence supports it.
  5. Report what is known, what remains uncertain, and the next useful check.

Leaving investigation mode

Leave this mode only when the user explicitly ends the investigation or authorizes a specific change. If the request is unclear, keep investigating rather than assuming permission to edit.