Smt E2E Dataflow Debugging
GoogleCloudPlatform/DataflowTemplates
Debugs logical errors and data discrepancies in Dataflow templates by launching jobs via Terraform and comparing source (e.g.
Diagnose a reported application failure on explicitly authorized remote hosts using bounded logs and runtime evidence.
Install Remote Debugging
$ npx skills add WrongStack/WrongStack --skill remote-debugging -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install WrongStack/WrongStack remote-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/remote-debugging .claude/skills/remote-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 "remote-debugging" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/remote-debugging into .claude/skills/remote-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remote-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/remote-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 remote-debugging -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install WrongStack/WrongStack remote-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/remote-debugging .agents/skills/remote-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 "remote-debugging" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/remote-debugging into .agents/skills/remote-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remote-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 remote-debugging -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install WrongStack/WrongStack remote-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/remote-debugging .cursor/skills/remote-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 "remote-debugging" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/remote-debugging into .cursor/skills/remote-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remote-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/remote-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 remote-debugging -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install WrongStack/WrongStack remote-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/remote-debugging .gemini/skills/remote-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 "remote-debugging" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/remote-debugging into .gemini/skills/remote-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remote-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 remote-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 remote-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/remote-debugging .github/skills/remote-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 "remote-debugging" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/remote-debugging into .github/skills/remote-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remote-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 remote-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 remote-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/remote-debugging .opencode/skills/remote-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 "remote-debugging" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/remote-debugging into .opencode/skills/remote-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remote-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
remote-debugging- GitHub stars
- 371
- Token cost
- ~868 tokens
- SKILL.md length
- 320 words
- Files
- 1
- Skills in repo
- 100
- Repo updated
- First seen
- Licence
- MIT
At a glance
Diagnose a reported application failure on explicitly authorized remote hosts using bounded logs and runtime evidence.
- Works in 6 steps: Pin the symptom, expected behavior, time… → Capture running process/image/revision,… → Use bounded log/profile windows and… → …
- Local behavior differs from a known server
- 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
Remote Debugging is an agent skill from WrongStack/WrongStack. Diagnose a reported application failure on explicitly authorized remote hosts using bounded logs and runtime evidence. Use when local behavior differs from a known server or deployment; start read-only and keep diagnosis separate from disruptive remediation.
Its SKILL.md is about 870 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. 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
- Local behavior differs from a known server
- Start read-only and keep diagnosis separate from disruptive remediation
Example prompts
- “/remote-debugging”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Pin the symptom, expected behavior, time window and affected authorized service.
- Capture running process/image/revision, effective non-secret config and resource signals before proposing a fix.
- Use bounded log/profile windows and minimize sensitive data capture; whole env dumps are not diagnostics.
- Distinguish disk/memory/network/service conditions from application errors using evidence.
- Preserve the live access path; restarts, tracing overhead and data changes need authorization within the maintenance task.
- No broad discovery, third-party probing or access-control workarounds. A missing boundary is a diagnosis gap.
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):
freedesktop.orgopentelemetry.io
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
Remote Debugging loads about 868 tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 320 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). 320 words, ~868 tokens.
Download SKILL.mdSave it as
.claude/skills/remote-debugging/SKILL.md (or your agent's skills folder).- name
- remote-debugging
- description
- Diagnose a reported application failure on explicitly authorized remote hosts using bounded logs and runtime evidence. Use when local behavior differs from a known server or deployment; start read-only and keep diagnosis separate from disruptive remediation.
- trigger
- Diagnose a reported application failure on explicitly authorized remote hosts using bounded logs and runtime evidence. Use when local behavior differs from a…
- version
- 1.0.1
- required-capabilities
- filesystem.read
- optional-capabilities
- filesystem.write, execution.shell, verification.run, web.research
- metadata.routing-group
- operations
- metadata.domain
- operations
Remote Debugging
Selection card
- Task: Diagnose remote processes and networking over SSH. / TR: SSH üzerinden uzak süreç ve ağı 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 a reported application failure on explicitly authorized remote hosts using bounded logs and runtime evidence.
Verify the actual runtime/package/container versions and source identity on the target; current host facts outrank assumptions from local builds.
Rules
- Pin the symptom, expected behavior, time window and affected authorized service.
- Capture running process/image/revision, effective non-secret config and resource signals before proposing a fix.
- Use bounded log/profile windows and minimize sensitive data capture; whole env dumps are not diagnostics.
- Distinguish disk/memory/network/service conditions from application errors using evidence.
- Preserve the live access path; restarts, tracing overhead and data changes need authorization within the maintenance task.
- No broad discovery, third-party probing or access-control workarounds. A missing boundary is a diagnosis gap.
Workflow
- Connect through the approved SSH/observability surface.
- Read service status, focused logs and relevant deployment/config differences.
- Form one hypothesis and run the least disruptive bounded check.
- Apply only requested/authorized remediation and verify the actual remote behavior.
- Remove owned temporary instrumentation and state any remaining live risk/uncertainty.
Before returning
Remote identity and symptom captured; evidence supports the cause; remediation scope and actual health stated; secrets/instrumentation handled.
Sources
Versioned facts checked 2026-10-09; refresh authoritative sources before new installs/upgrades. systemd journal, OpenTelemetry.
Skills in scope
- ssh-operations — connect to and administer explicitly authorized hosts through OpenSSH with verified identity and bounded operations.
- linux-service-ops — configure and troubleshoot application services on an authorized Linux host with explicit service ownership.
- debugging — debugging contracts and verification.
- incident-response — diagnose and recover an owned service incident with bounded changes, timeline evidence and verified health. Use during outages, bad deployments or data/service degradation; preserve evidence and separate mitigation from root-cause repair.
© 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/remote-debugging of WrongStack/WrongStack.
Open the folder on GitHubat commit a744bdc
Compare with similar skills
Remote 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 |
|---|---|---|---|---|---|---|
| Remote Debugging this skillWrongStack/WrongStack | 371 | — | ~868 | Automated safety check: Pass | MIT | |
| Smt E2E Dataflow DebuggingGoogleCloudPlatform/DataflowTemplates | 1.3k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Claude Session Router Debuggerweave-os/router | 5.6k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Logging Patternsdecebals/claude-code-java | 751 | 1 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Burla Parallel Dev ClustersBurla-Cloud/burla | 263 | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Code Reviewaide-family/moon | 253 | — | ~815 | Automated safety check: Pass | None |
Similar skills
Claude Session Router Debugger
weave-os/router
Correlates a Claude Code session's local transcript with a model router's production cloud logs to explain why a specific response rendered the way it did.
Logging Patterns
decebals/claude-code-java
Java logging best practices with SLF4J, structured logging (JSON), and MDC for request tracing.
Burla Parallel Dev Clusters
Burla-Cloud/burla
Sets up an isolated Burla dev cluster per git worktree so several agents can work in parallel, and explains when to use local-dev or remote-dev.
Code Review
aide-family/moon
Reviews code for correctness and potential bugs, pinpoints bug locations by file and line, and suggests concrete fixes.
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…
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
Categories
Questions about Remote Debugging
What does Remote Debugging do?
Diagnose a reported application failure on explicitly authorized remote hosts using bounded logs and runtime evidence. Remote Debugging is an agent skill from WrongStack/WrongStack. Diagnose a reported application failure on explicitly authorized remote hosts using bounded logs and runtime evidence.
When should I use Remote Debugging?
Remote Debugging fits situations like: local behavior differs from a known server; start read-only and keep diagnosis separate from disruptive remediation.
How do I install Remote Debugging in Claude Code?
Run `npx skills add WrongStack/WrongStack --skill remote-debugging -a claude-code`. Or copy the skill folder (packages/core/skills/remote-debugging in WrongStack/WrongStack) into .claude/skills/remote-debugging in your project. Claude Code loads it when a task matches its description.
How do I install Remote Debugging in Codex?
Run `npx skills add WrongStack/WrongStack --skill remote-debugging -a codex`. Or copy the skill folder (packages/core/skills/remote-debugging in WrongStack/WrongStack) into .agents/skills/remote-debugging in your project. Codex loads it when a task matches its description.
Can I use Remote 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 remote-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/remote-debugging, .gemini/skills/remote-debugging, .github/skills/remote-debugging and .opencode/skills/remote-debugging in your project.
What does Remote Debugging need to run?
SKILL.md names no scripts, command-line tools or credentials: Remote Debugging is instructions for the agent only.
Does Remote Debugging access the network?
SKILL.md names 2 domains. As links in the text: freedesktop.org and opentelemetry.io. This is read from the text; nothing was executed.
Is Remote 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 Remote Debugging use?
Remote 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 Remote Debugging use?
About 868 tokens (SKILL.md is roughly 3.5k 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 Remote Debugging?
Skills that share tags, products or a category with Remote Debugging: Smt E2E Dataflow Debugging (GoogleCloudPlatform/DataflowTemplates, 1.3k stars), Claude Session Router Debugger (weave-os/router, 5.6k stars), Logging Patterns (decebals/claude-code-java, 751 stars) and Burla Parallel Dev Clusters (Burla-Cloud/burla, 263 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Remote 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.