traceback-condensing SKILL.md skillA
traceback-condensing from apatheticmioz/castor is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add apatheticmioz/castor/traceback-condensing@git:20261003.980fb6aPins git:20261003.980fb6a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- apatheticmioz/castor
- Path
skills/traceback-condensing/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261003.980fb6a, committed Oct 3, 2026
- Size
- 1,235 bytes
- Repository stars
- 12
- License
- AGPL-3.0
Condense a failing test run into a minimal failure digest before retrying.
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
# Traceback Condensing When a test run or build fails, do NOT paste the raw multi-hundred-line traceback into your reasoning. Condense it into a compact failure digest first, then act on the digest. ## Checklist 1. Identify the FIRST user-code frame (skip site-packages, stdlib, and framework internals). That is where the real bug lives. 2. Extract the exact file, line, and symbol from that frame. 3. Capture the assertion message or exception type + message verbatim. 4. Reduce the digest to at most ~100 tokens: `[FailureDigest] <type> at <file>:<line> in <symbol>: <message>` 5. Use the digest (not the raw traceback) to form your next hypothesis. ## Rules - Never re-emit the full traceback into a tool call or the final answer. - If the digest points at a test file (not source), the bug is likely in the code under test — go read that source file next. - If the digest is a network/timeout error, that is an environment issue, not a code bug — say so and do not "fix" unrelated code.
Read the whole file at its exact version.
How to install
mdr add apatheticmioz/castor/traceback-condensing@sha256:3709d950aed3f3fcThe line at the top of this page pins the label git:20261003.980fb6a, 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_oxpj7hmgivazbgbz)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 3, 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 (1235 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
apatheticmioz/castor · 12 stars · license AGPL-3.0 · pushed 2026-10-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_oxpj7hmgivazbgbz GET https://markdownregistry.com/api/v1/resolve?ref=apatheticmioz/castor/traceback-condensing GET https://markdownregistry.com/api/v1/blob/3709d950aed3f3fc23673a38cff6ca5549577bfb74f32d9ff882d2248c26f882
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.