dig

Other Community

Skill notes

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.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
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 explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# 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

1. Clarify the goal and constraints (what needs to be understood, scope, deadlines).
2. Gather context by reading relevant files, logs, configs, or outputs.
3. Ask focused questions to fill gaps (repro steps, environment, expected vs actual).
4. Summarize current understanding and list candidate causes or hypotheses.
5. 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.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.