القائمة
Capture the host's environment, working directory, recent git activity, and pipeline-relevant state so you can diagnose "what's actually happening on the machine".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
How to build a NEW tool of your own by writing its code in your sandbox, testing it, and forging it into a live, callable tool with `env(action="forge_tool")`. Use when no existing tool does what you need and you can implement it as a small script. Multiple tools + skills can be saved together as one reusable Sandbox Tool Pack.
How to inspect and edit your OWN operating environment at runtime — system prompt, active tools, and skills — using the `env` tool. Use when you need to change your own capabilities (turn a tool on/off, rewrite your instructions, author a new skill) or save them for this session.
Run the same task on a recurring cron schedule. Parses interval syntax (5m, 2h, 1d, "*/15 * * * *"), records the schedule, and acknowledges back to the user.
Review code in the current working tree across three independent dimensions (reuse, quality, efficiency) and synthesise a small punch-list of high-value cleanups.
Interview the user about a workflow they keep repeating, then generate a reusable SKILL.md and write it to disk so the next session starts with the skill already loaded.
Apply the same prompt or operation to a list of items in turn, collecting results. Useful for "do X to each of these files / PRs / records" tasks.
| name | Debug Snapshot |
| description | Capture the host's environment, working directory, recent git activity, and pipeline-relevant state so you can diagnose "what's actually happening on the machine". |
| category | diagnostic |
| effort | medium |
| when_to_use | When the user reports something acting weird, a tool calls fail unexpectedly, or you need to "ground" your reasoning in the real machine state before suggesting fixes. Don't use this just to look around — use it when there's a concrete problem to triangulate. |
| allowed_tools | ["Read","Glob"] |
| shell | bash |
| shell_timeout_s | 20 |
| version | 1.0.0 |
The captured snapshot below is the ground truth. Read it carefully before suggesting any fix — many "obvious" fixes are wrong because the bug is one layer up (wrong PATH, wrong cwd, stale lock file, unset env var, dirty worktree).
id -unid -Gnhostnameuptimepwd[ -w "$(pwd)" ] && echo yes || echo nodf -h "$(pwd)" 2>/dev/null | tail -n 1 || echo "(df failed)"df -i "$(pwd)" 2>/dev/null | tail -n 1 || echo "(df failed)"find . -maxdepth 3 -type f -mmin -5 -not -path "*/node_modules/*" -not -path "*/.git/*" -not -path "*/__pycache__/*" 2>/dev/null | head -n 20
git log --oneline --decorate -n 10 2>/dev/null || echo "(not a git repo)"
{ ss -tln 2>/dev/null || netstat -tln 2>/dev/null || lsof -iTCP -sTCP:LISTEN -n 2>/dev/null; } | head -n 30
free -h 2>/dev/null | head -n 2 || echo "(free unavailable)"cat /proc/loadavg 2>/dev/null || uptime | sed 's/.*load average: //'ulimit -nenv | grep -E '^(PATH|PYTHONPATH|NODE_ENV|VIRTUAL_ENV|HOME|USER|LANG|TZ|GENY_|ANTHROPIC_|OPENAI_)' | sed 's/=\(sk-\|ghp_\|gho_\)[A-Za-z0-9_-]*/=<redacted>/'
The data above is the input — your job is the output:
If the snapshot looks clean and you can't tie anything to the symptom, say so plainly and ask for a more specific reproducer.