Dotnet Debugging
novotnyllc/dotnet-artisan
Debugs Windows and Linux/macOS applications (native, .NET/CLR, mixed-mode) with WinDbg MCP (crash dumps, !analyze, !syncblk, !dlk, !runaway, !dumpheap, !gcroot, BSOD), dotnet-dump, lldb with SOS…
Diagnose reported container build, startup, network, permission and resource failures.
Install Container Debugging
$ npx skills add WrongStack/WrongStack --skill container-debugging -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install WrongStack/WrongStack container-debugging --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/WrongStack/WrongStack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/core/skills/container-debugging .claude/skills/container-debugging && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "container-debugging" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/container-debugging into .claude/skills/container-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "container-debugging", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/container-debuggingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add WrongStack/WrongStack --skill container-debugging -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install WrongStack/WrongStack container-debugging --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WrongStack/WrongStack.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/core/skills/container-debugging .agents/skills/container-debugging && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "container-debugging" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/container-debugging into .agents/skills/container-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "container-debugging", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add WrongStack/WrongStack --skill container-debugging -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install WrongStack/WrongStack container-debugging --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WrongStack/WrongStack.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/core/skills/container-debugging .cursor/skills/container-debugging && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "container-debugging" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/container-debugging into .cursor/skills/container-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "container-debugging", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/WrongStack/WrongStack.git --path packages/core/skills/container-debugging--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add WrongStack/WrongStack --skill container-debugging -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install WrongStack/WrongStack container-debugging --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WrongStack/WrongStack.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/core/skills/container-debugging .gemini/skills/container-debugging && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "container-debugging" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/container-debugging into .gemini/skills/container-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "container-debugging", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install WrongStack/WrongStack container-debuggingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add WrongStack/WrongStack --skill container-debugging -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/WrongStack/WrongStack.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/core/skills/container-debugging .github/skills/container-debugging && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "container-debugging" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/container-debugging into .github/skills/container-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "container-debugging", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add WrongStack/WrongStack --skill container-debugging -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install WrongStack/WrongStack container-debugging --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WrongStack/WrongStack.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/core/skills/container-debugging .opencode/skills/container-debugging && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "container-debugging" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/container-debugging into .opencode/skills/container-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "container-debugging", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
container-debugging- GitHub stars
- 371
- Token cost
- ~782 tokens
- SKILL.md length
- 276 words
- Files
- 1
- Skills in repo
- 100
- Repo updated
- First seen
- Licence
- MIT
At a glance
Diagnose reported container build, startup, network, permission and resource failures.
- Works in 6 steps: Pin Docker context, container/image… → Distinguish build-stage dependencies… → Inspect exit code, focused logs and… → …
- Compose service fails
- SKILL.md covers Selection card, Overview, Rules and Workflow, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Container Debugging is an agent skill from WrongStack/WrongStack. Diagnose reported container build, startup, network, permission and resource failures. Use when an image or Compose service fails; reproduce against the final image/config and avoid data-destroying cleanup as a workaround.
Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Debugging and Containers. It works with Docker. The repository describes itself as: An AI coding agent that reads your code, edits files, runs commands, and reasons through bugs — across a terminal REPL, a full-screen TUI, and a browser UI, while you keep your… The licence is MIT.
When your agent uses it
- Compose service fails
- Reproduce against the final image/config and avoid data-destroying cleanup as a workaround
Example prompts
- “/container-debugging”
Requirements
- Docker
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Pin Docker context, container/image digest, platform, effective command and environment.
- Distinguish build-stage dependencies from final runtime files, dynamic libraries and writable paths.
- Inspect exit code, focused logs and health command before changing timeout/restart policy.
- Check namespace-specific network/DNS assumptions and service names on the actual network.
- Diagnose UID/GID and bind-volume permissions without broadly making paths world-writable.
- Keep production data/images/evidence intact; cache deletion, pruning and volume removal require a specific supported reason.
What it can do on your machine
Read from SKILL.md and the folder at commit a744bdc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.docker.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Container Debugging loads about 782 tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 276 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from WrongStack/WrongStack at commit a744bdc, republished under its MIT licence (© WrongStack). 276 words, ~782 tokens.
Download SKILL.mdSave it as
.claude/skills/container-debugging/SKILL.md (or your agent's skills folder).- name
- container-debugging
- description
- Diagnose reported container build, startup, network, permission and resource failures. Use when an image or Compose service fails; reproduce against the final image/config and avoid data-destroying cleanup as a workaround.
- trigger
- Diagnose reported container build, startup, network, permission and resource failures. Use when an image or Compose service fails; reproduce against the final…
- version
- 1.0.1
- required-capabilities
- filesystem.read
- optional-capabilities
- filesystem.write, execution.shell, verification.run, web.research
- metadata.routing-group
- operations
- metadata.domain
- containers
Container Debugging
Selection card
- Task: Diagnose a running container failure. / TR: Çalışan container hatasını teşhis et.
- Start: Identify the authorized target, current health and rollback boundary.
- Finish: apply the acceptance checks below; report observed results and unresolved constraints.
Overview
Diagnose reported container build, startup, network, permission and resource failures.
Current checked engine target is Docker 29.9.0. Inspect actual daemon/client/build runtime and platform; build success and final-stage startup are separate checks.
Rules
- Pin Docker context, container/image digest, platform, effective command and environment.
- Distinguish build-stage dependencies from final runtime files, dynamic libraries and writable paths.
- Inspect exit code, focused logs and health command before changing timeout/restart policy.
- Check namespace-specific network/DNS assumptions and service names on the actual network.
- Diagnose UID/GID and bind-volume permissions without broadly making paths world-writable.
- Keep production data/images/evidence intact; cache deletion, pruning and volume removal require a specific supported reason.
Workflow
- Reproduce the failure with the exact image/config and bounded checks.
- Trace build output or startup failure to the responsible layer/path.
- Compare working local conditions with the image/host platform.
- Make the narrow Dockerfile/config/application repair.
- Rebuild/run the final stage and verify health, signals and the failing user path.
Before returning
Correct context/image/config tested; cause backed by logs/state; final-stage behavior verified; data and unrelated containers preserved.
Sources
Versioned facts checked 2026-10-09; refresh authoritative sources before new installs/upgrades. Docker troubleshooting, Docker build practices.
Skills in scope
- docker-deploy — docker deploy contracts and verification.
- compose-operations — operate and evolve multi-service Docker Compose environments with explicit networks, volumes and environment boundaries.
- linux-service-ops — configure and troubleshoot application services on an authorized Linux host with explicit service ownership.
- debugging — debugging contracts and verification.
© WrongStack, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in packages/core/skills/container-debugging of WrongStack/WrongStack.
Open the folder on GitHubat commit a744bdc
Compare with similar skills
Container Debugging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Container Debugging this skillWrongStack/WrongStack | 371 | — | ~782 | Automated safety check: Pass | MIT | |
| Dotnet Debuggingnovotnyllc/dotnet-artisan | 232 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Linux Vm Testnubjs/nub | 4.4k | — | ~986 | Automated safety check: Pass | MIT | |
| Localnetboundless-xyz/boundless | 193 | — | ~1.8k | Automated safety check: Notes | Apache-2.0 | |
| Debugging Local Task Agent RunsPostHog/posthog | 40k | — | ~2.1k | Automated safety check: Notes | Custom licence | |
| Borg Live Debugkaranhudia/borg-ui | 1.7k | — | ~1.4k | Automated safety check: Notes | AGPL-3.0 |
Similar skills
Linux Vm Test
nubjs/nub
Run ad-hoc Nub tests and debugging probes on real local Linux guests.
Localnet
boundless-xyz/boundless
Start and interact with the Boundless localnet (docker compose-based local development network).
- Official
Debugging Local Task Agent Runs
PostHog/posthog
Debug the output of local PostHog task runs — the wizard cloud-run path that executes inside a Docker sandbox under the local Temporal process-task workflow (the wizard that integrates PostHog, then…
Borg Live Debug
karanhudia/borg-ui
Live Borg debugging by exec-ing into the borg-web-ui Docker container.
- Official
.NET Crash Dump Collection
dotnet/skills
Configures automatic crash dumps or captures dumps from running processes for modern .NET apps on Linux, macOS and Windows, including Docker and Kubernetes.
More from WrongStack/WrongStack
All 100 skills in this repoTech Stack
WrongStack/WrongStack
Validate and upgrade dependencies against live registries and official migration guides in any ecosystem.
Skill Creator
WrongStack/WrongStack
Create, improve and validate WrongStack SKILL.md bundles with precise discovery, progressive resources and current runtime contracts.
Bug Hunter
WrongStack/WrongStack
A skill your agent uses when scanning source code for bugs, anti-patterns, code smells, or quality issues in a codebase, or when running a proof-driven bug hunt that must find, prove, fix, and…
Design Craft
WrongStack/WrongStack
Design or substantially improve user-facing interfaces with a product-specific visual direction, content hierarchy, and rendered critique.
Design Critique
WrongStack/WrongStack
A skill your agent uses to audit an interface that already exists and say precisely why it looks generated, templated, or unfinished — a scored rubric across composition, typography, color, states…
Mailbox Bridge
WrongStack/WrongStack
A skill your agent uses when external coding agents (Claude Code, Aider, custom scripts) need to participate in the project's shared WrongStack mailbox, or when a user asks to "expose the mailbox"…
Related
Works with
Categories
Questions about Container Debugging
What does Container Debugging do?
Diagnose reported container build, startup, network, permission and resource failures. Container Debugging is an agent skill from WrongStack/WrongStack. Diagnose reported container build, startup, network, permission and resource failures.
When should I use Container Debugging?
Container Debugging fits situations like: compose service fails; reproduce against the final image/config and avoid data-destroying cleanup as a workaround.
How do I install Container Debugging in Claude Code?
Run `npx skills add WrongStack/WrongStack --skill container-debugging -a claude-code`. Or copy the skill folder (packages/core/skills/container-debugging in WrongStack/WrongStack) into .claude/skills/container-debugging in your project. Claude Code loads it when a task matches its description.
How do I install Container Debugging in Codex?
Run `npx skills add WrongStack/WrongStack --skill container-debugging -a codex`. Or copy the skill folder (packages/core/skills/container-debugging in WrongStack/WrongStack) into .agents/skills/container-debugging in your project. Codex loads it when a task matches its description.
Can I use Container Debugging in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add WrongStack/WrongStack --skill container-debugging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/container-debugging, .gemini/skills/container-debugging, .github/skills/container-debugging and .opencode/skills/container-debugging in your project.
What does Container Debugging need to run?
SKILL.md names no scripts, command-line tools or credentials: Container Debugging is instructions for the agent only. Our summary lists: Docker.
Does Container Debugging access the network?
SKILL.md names 1 domain. As links in the text: docs.docker.com. This is read from the text; nothing was executed.
Is Container Debugging safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Container Debugging use?
Container Debugging is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Container Debugging use?
About 782 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Container Debugging?
Skills that share tags, products or a category with Container Debugging: Dotnet Debugging (novotnyllc/dotnet-artisan, 232 stars), Linux Vm Test (nubjs/nub, 4.4k stars), Localnet (boundless-xyz/boundless, 193 stars) and Debugging Local Task Agent Runs (PostHog/posthog, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Container Debugging?
WrongStack (a GitHub organization) maintains it in WrongStack/WrongStack, which has 371 GitHub stars. The repository holds 100 skills in this directory. The repository was last updated on October 10, 2026.
Source: WrongStack/WrongStack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.