trace SKILL.md skillA
trace from naimkatiman/continuous-improvement is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add naimkatiman/continuous-improvement/trace@git:20260906.bface5cPins git:20260906.bface5c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- naimkatiman/continuous-improvement
- Path
third-party/oh-my-claudecode/skills/trace/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260906.bface5c, committed Sep 6, 2026
- First version recorded
- May 3, 2026
- Size
- 10,381 bytes
- Repository stars
- 9
- License
- MIT
Evidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode.
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
# Trace Skill Use this skill for ambiguous, causal, evidence-heavy questions where the goal is to explain **why** an observed result happened, not to jump directly into fixing or rewriting code. This is the orchestration layer on top of the built-in `tracer` agent. The goal is to make tracing feel like a reusable OMC operating lane: restate the observation, generate competing explanations, gather evidence in parallel, rank the explanations, and propose the next probe that would collapse uncertainty fastest. ## Good entry cases Use `/oh-my-claudecode:trace` when the problem is: - ambiguous - causal - evidence-heavy - best answered by exploring competing explanations in parallel Examples: - runtime bugs and regressions - performance / latency / resource behavior - architecture / premortem / postmortem analysis - scientific or experimental result tracing - config / routing / orchestration behavior explanation - “given this output, trace back the likely causes” ## Core tracing contract Always preserve these distinctions: 1. **Observation** -- what was actually observed 2. **Hypotheses** -- competing explanations 3. **Evidence For** -- what supports each explanation …
Read the whole file at its exact version.
How to install
mdr add naimkatiman/continuous-improvement/trace@sha256:e82ccaa563f70380The line at the top of this page pins the label git:20260906.bface5c, 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_t2uoulldxpwcr76l)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 3, 2026 and Sep 6, 2026, about one every 127 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260906.bface5c latest | 2026-09-06 | bface5c | 10,381 B | A | view · diff |
| git:20260503.16cdfd3 | 2026-05-03 | 16cdfd3 | 9,690 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 (10381 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
naimkatiman/continuous-improvement · 9 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t2uoulldxpwcr76l GET https://markdownregistry.com/api/v1/resolve?ref=naimkatiman/continuous-improvement/trace GET https://markdownregistry.com/api/v1/blob/e82ccaa563f703803ad92093766ada969188df44b9ee91298a26b8c3d0792b0e
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.
More from naimkatiman/continuous-improvement
Every file in naimkatiman/continuous-improvement