# Relay10 Debug

> Diagnose a failure from reproducible evidence and isolate its root cause. Use for regressions, flaky behavior, stuck automation, or failed checks; edit only when the user also asked for a fix.

- **Type:** Skill
- **Install:** `agentstack add skill-minwoo19930301-relay10-relay10-debug`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [minwoo19930301](https://agentstack.voostack.com/s/minwoo19930301)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [minwoo19930301](https://github.com/minwoo19930301)
- **Source:** https://github.com/minwoo19930301/relay10/tree/main/plugins/relay10/skills/relay10-debug

## Install

```sh
agentstack add skill-minwoo19930301-relay10-relay10-debug
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# DisciplinedRun Debug

Prefer one falsifiable hypothesis over a sequence of speculative patches.

## Diagnostic loop

1. Capture the exact symptom, environment, expected behavior, and first known failure.
2. Reproduce with the smallest safe command or fixture.
3. Locate the failing boundary: input, configuration, process, network, storage, adapter, or output.
4. Collect evidence on both sides of that boundary.
5. State one hypothesis and the observation that would falsify it.
6. Run the smallest experiment that distinguishes competing causes.
7. If a fix is authorized, apply the minimal repair and add a regression check.

After three materially similar failed repair attempts, stop patching. Revisit the reproduction, boundary, and assumptions.

## Authorization boundary

A request to diagnose does not authorize code changes. A request to fix does not automatically authorize data deletion, credential changes, deployment, or publication. Use backup-first procedures for stateful repair.

## Output contract

Return:

- reproduced symptom and command;
- root cause with evidence, or ranked remaining hypotheses;
- affected and unaffected boundaries;
- fix and regression test, if authorized;
- operational risks and rollback.

Distinguish a health label such as `connected` or `configured` from proof that useful work completed.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [minwoo19930301](https://github.com/minwoo19930301)
- **Source:** [minwoo19930301/relay10](https://github.com/minwoo19930301/relay10)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-minwoo19930301-relay10-relay10-debug
- Seller: https://agentstack.voostack.com/s/minwoo19930301
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.