trace SKILL.md skillA
trace from stevepolitodesign/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add stevepolitodesign/skills/trace@git:20260928.afcb292Pins git:20260928.afcb292 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- stevepolitodesign/skills
- Path
trace/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260928.afcb292, committed Sep 28, 2026
- Size
- 7,945 bytes
- Repository stars
- 5
- License
- none declared
Run a scenario and record what actually happened.
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
Reading code tells you what *should* happen. Running it tells you what does: the
callback nobody mentioned, the job that enqueues two more, the email that goes out
twice. That's the gap this fills. The output is a record, in order, of what one
scenario did when it ran, with every step marked as seen or only read.
Two ways this fails. You read the code, write it up in the past tense, and it looks
exactly like a run — so the reader trusts a guess as much as an observation. Or you
run a step that can't be undone: a process gets killed, a database gets dropped. The
first is worse, because nothing about it looks wrong.
## 1. Pin the scenario
The scenario is `$ARGUMENTS`, or ask for one. It arrives as a sentence ("user creates
an account"), a route, a command, a job name.
Turn it into three things before running anything:
- **Entry point.** The route and handler, CLI command, or job that starts it — found
in the code, not assumed. Two plausible ones (sign up by form, sign up by invite)?
Take the common one, say which, and name the other as its own trace.
- **Starting state.** Who is acting and what exists already. "A signed-in user who
…Read the whole file at its exact version.
How to install
mdr add stevepolitodesign/skills/trace@sha256:fb43d0dc25dbaecbThe line at the top of this page pins the label git:20260928.afcb292, 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_xtem5ei25hobav3a)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 28, 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 (7945 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
stevepolitodesign/skills · 5 stars · license none declared · pushed 2026-10-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xtem5ei25hobav3a GET https://markdownregistry.com/api/v1/resolve?ref=stevepolitodesign/skills/trace GET https://markdownregistry.com/api/v1/blob/fb43d0dc25dbaecb0e33d11d0c694cd19162b8760702a842d8fc84275254108a
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 stevepolitodesign/skills
Every file in stevepolitodesign/skills