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.
Install
$ agentstack add skill-minwoo19930301-relay10-relay10-debug ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-minwoo19930301-relay10-relay10-debug) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
DisciplinedRun Debug
Prefer one falsifiable hypothesis over a sequence of speculative patches.
Diagnostic loop
- Capture the exact symptom, environment, expected behavior, and first known failure.
- Reproduce with the smallest safe command or fixture.
- Locate the failing boundary: input, configuration, process, network, storage, adapter, or output.
- Collect evidence on both sides of that boundary.
- State one hypothesis and the observation that would falsify it.
- Run the smallest experiment that distinguishes competing causes.
- 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
- Source: minwoo19930301/relay10
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.