Runtime Debug
SkillCloud & infraGuides your agent through diagnosing module bundling and resolution regressions in Next.js builds.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Runtime Debug skill
About this capability
Debug broken runtime/environments by checking logs and observability first, then code. Use when a URL, deploy, or ephemeral/CI environment fails at runtime rather than a local code bug.
What this skill tells your AI
The instructions your AI receives, as published by outthislife/brooklyn-skills in skills/runtime-debug/SKILL.md and read by ahel’s review.
When something breaks at runtime (a URL 500s, a deploy is down, an ephemeral env misbehaves), look at what actually happened before editing code.
Steps
- Reproduce and capture the real failure (status, error, request id, time).
- Check observability first: logs, traces, metrics. Use an observability MCP (e.g. Datadog) if one is available/connected; otherwise fall back to the platform's log stream (CI job, container, Jenkins, cloud logs).
- Locate the failing service/line from the evidence, not a guess.
- Fix the real cause. Don't add logging-only "fixes" and call it done.
- For intentional lab/ephemeral config (test secrets, fail-open), don't raise false alarms — leave required env in place.
Don't
- Rewrite code speculatively before reading logs.
- Report fixed without re-checking the runtime.
Signals
- GitHub stars
- 192
- Forks
- 6
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
runtime-debug- Source
- github.com/outthislife/brooklyn-skills