debug-failed-run SKILL.md skillA
debug-failed-run from nebius/nebius-physical-ai is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nebius/nebius-physical-ai/debug-failed-run@git:20261002.bccd515Pins git:20261002.bccd515 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nebius/nebius-physical-ai
- Path
skills/atomic/debug-failed-run/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261002.bccd515, committed Oct 2, 2026
- First version recorded
- Aug 17, 2026
- Size
- 12,674 bytes
- Repository stars
- 106
- License
- Apache-2.0
Use when a workflow run failed, hung, or produced no artifacts — an ordered triage from run id to root cause across status, stage logs, S3 evidence, pod-level reasons, and the resume-vs-cancel decision.
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
# Debug a failed workflow run Start from the run id and work outward. Every step below is read-only until the final decision, so none of it costs GPU time or destroys the evidence you need. ## 0. Find the run id ```bash npa workbench workflow list --project <alias> --limit 50 --json ``` Runs are durable S3 objects, so this works after the controller, the cluster, or your shell is gone. If you only have an S3 prefix, every command below accepts an `s3://` run prefix wherever it accepts a run id. ## 1. Status first — it names the failure class ```bash npa workbench workflow status <run-id> --project <alias> --json ``` This is the single most informative command, because **for a PENDING job it reports the pod-level reason** rather than just "pending". That distinction is the whole triage: - `PENDING` + `ImagePullBackOff` → registry problem, go to step 4. The job will never fail on its own; Kubernetes retries pulls forever. - `PENDING` + `Unschedulable` → capacity or accelerator-name problem, step 5. - `FAILED` → the payload ran and exited non-zero, step 3. - `FAILED_STARTUP` → the controller itself failed identically several times …
Read the whole file at its exact version.
How to install
mdr add nebius/nebius-physical-ai/debug-failed-run@sha256:3403ed298a7fba6cThe line at the top of this page pins the label git:20261002.bccd515, 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_ecsit4ekqtedmonr)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Aug 17, 2026 and Oct 2, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261002.bccd515 latest | 2026-10-02 | bccd515 | 12,674 B | A | view · diff |
| git:20261001.0555584 | 2026-10-01 | 0555584 | 12,238 B | A | view · diff |
| git:20260917.a8b1c33 | 2026-09-17 | a8b1c33 | 11,643 B | A | view · diff |
| git:20260830.7e83781 | 2026-08-30 | 7e83781 | 8,615 B | A | view · diff |
| git:20260823.224d9da | 2026-08-23 | 224d9da | 7,780 B | A | view · diff |
| git:20260817.be3cf06 | 2026-08-17 | be3cf06 | 7,729 B | A | view |
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 (12674 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
nebius/nebius-physical-ai · 106 stars · license Apache-2.0 · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ecsit4ekqtedmonr GET https://markdownregistry.com/api/v1/resolve?ref=nebius/nebius-physical-ai/debug-failed-run GET https://markdownregistry.com/api/v1/blob/3403ed298a7fba6c4b3f3621e9244b6420b7cfcdb58e12c4cd85e72176bcf751
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.