code-troubleshooting SKILL.md skillA
code-troubleshooting from berylliumsec/nebula is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add berylliumsec/nebula/code-troubleshooting@git:20261013.1053351Pins git:20261013.1053351 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- berylliumsec/nebula
- Path
.agents/skills/code-troubleshooting/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261013.1053351, committed Oct 13, 2026
- Size
- 2,664 bytes
- Repository stars
- 1,141
- License
- BSD-2-Clause
Diagnose Nebula code defects, regressions, and failing behavior before a fix. Use when troubleshooting may lead to a code or configuration change.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Code Troubleshooting Find and validate the causal fault before changing behavior. A symptom, stack trace, correlation, or plausible patch is not a root cause. ## Establish the cause 1. Capture the expected and observed behavior, affected build and environment, and a minimal reproduction or durable failure trace. Identify where the first incorrect state or result appears. 2. Trace that state through the responsible code and its callers, inputs, and owners. Form a causal explanation of how the fault produces the symptom, then check at least one credible alternative against the evidence. Use read-only inspection, targeted reproduction, or temporary diagnostic probes as needed; do not make a behavior-changing repair during diagnosis. 3. State the proposed root cause with the specific code path and reproduction or trace that supports it. Mark any unresolved link as unknown and keep investigating rather than promoting an inference to a confirmed cause. ## Require independent subagent validation Before attempting a fix, start a separate subagent with fresh context (for Codex, `fork_turns: "none"`). Give it the original failure report, reproduction …
Read the whole file at its exact version.
How to install
mdr add berylliumsec/nebula/code-troubleshooting@sha256:200d4c0bac1eec61The line at the top of this page pins the label git:20261013.1053351, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_dcph2yg6edaqw6fj)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 13, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2664 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
berylliumsec/nebula · 1,141 stars · license BSD-2-Clause · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dcph2yg6edaqw6fj GET https://markdownregistry.com/api/v1/resolve?ref=berylliumsec/nebula/code-troubleshooting GET https://markdownregistry.com/api/v1/blob/200d4c0bac1eec6199577a3b356e0e14f2c695494a1efd398dd7157a708fef65
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.