dig
- Repo stars 39
- Author updated Live
- Author repo awesome-omni-skill
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @diegosouzapw · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: dig
description: Investigation-only mode for understanding bugs, features, or system behavior without making chan…
category: other
runtime: no special runtime
---
# dig output preview
## PART A: Task fit
- Use case: Investigation-only mode for understanding bugs, features, or system behavior without making changes. Use when the user says phrases like "let's investigate", "we need to figure out", or "we're debuggin", or asks to investigate or analyze before changing anything..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Overview / Trigger Phrases / Operating Rules” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Investigation-only mode for understanding bugs, features, or system behavior without making changes. Use when the user says phrases like "let's investigate", "we need to figure out", or "we're debuggin", or asks to investigate or analyze before changing anything.”.
- **02** When the source has headings, the agent prioritizes “Overview / Trigger Phrases / Operating Rules” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Overview / Trigger Phrases / Operating Rules”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: dig
description: Investigation-only mode for understanding bugs, features, or system behavior without making chan…
category: other
source: diegosouzapw/awesome-omni-skill
---
# dig
## When to use
- Investigation-only mode for understanding bugs, features, or system behavior without making changes. Use when the user…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Overview / Trigger Phrases / Operating Rules” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "dig" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Overview / Trigger Phrases / Operating Rules
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Dig
Overview
Run investigation-only mode to understand the situation before making any changes. Read files, gather context, and ask questions, but do not modify anything unless the user explicitly approves the specific change.
Trigger Phrases
Use this skill when the user indicates investigation or debugging intent, including:
- "let's investigate"
- "we need to figure out"
- "we're debuggin"
- Any request to investigate, analyze, or understand before changing code or configs
Operating Rules
- Do not edit files, run write operations, or make changes by default.
- Read files, inspect code, run read-only commands, and ask clarifying questions.
- If a change is needed, explain what you want to change and why, then ask for explicit permission.
- Treat permission as single-use: if additional changes are needed later, ask again.
- Stay in investigation mode until the user explicitly ends it.
Investigation Workflow
- Clarify the goal and constraints (what needs to be understood, scope, deadlines).
- Gather context by reading relevant files, logs, configs, or outputs.
- Ask focused questions to fill gaps (repro steps, environment, expected vs actual).
- Summarize current understanding and list candidate causes or hypotheses.
- Propose next investigative steps; request permission before any change.
Exiting Investigation Mode
Exit only when the user explicitly says something like "ok, we're done with investigation". If unclear, ask for confirmation before changing anything.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review