Trace how a subsystem works using code and runtime evidence. Use for architecture walkthroughs, data flow, call paths, and are-we-sure investigations.
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
# How
Build an evidence-backed explanation of how the requested subsystem works.
1. Find the public/consumer entry point, then trace data and control flow toward the effect. Do not start from filenames guessed by name alone.
2. Read the core types and state ownership before narrating individual functions.
3. Use `vcs`, tests, or `observe` when they resolve an ambiguity. If `delegate` exists, split independent exploration areas and reconcile them yourself.
4. Draw a compact text or Mermaid diagram when it reduces reader load.
5. Test at least one claim that could easily be wrong by running or inspecting the real path.
6. Explain in consumer order: trigger -> boundary -> state/transform -> side effect -> observable result. Name file/symbol evidence and uncertainty.
The line at the top of this page pins the label git:20260908.ec65ed5, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_hvyxngsrnwingpoo
GET https://markdownregistry.com/api/v1/resolve?ref=theonlyfusioncube/potetos-for-everyone/how
GET https://markdownregistry.com/api/v1/blob/d1a6101bd8b278127dbfba422aa9c9e1463392da3cfa0528b11923cf96b678e2
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.
theonlyfusioncube/potetos-for-everyone · automations/benny/skills/reproduce-and-fix-issues/SKILL.md · Reproduce a confirmed issue on the closest real surface, find root cause, and optionally prepare a minimal draft fix…
theonlyfusioncube/potetos-for-everyone · automations/benny/skills/triage-issue-reports/SKILL.md · Triage incoming software issue reports using available repository and runtime evidence, without editing code. Use for…
theonlyfusioncube/potetos-for-everyone · skills/architect/SKILL.md · Settle data shapes, ownership, boundaries, and interfaces before code crosses a function/module boundary. Use for…
theonlyfusioncube/potetos-for-everyone · skills/arena/SKILL.md · Spawn parallel candidate implementations for the same task, cross-judge, and graft the best parts into the winning…
theonlyfusioncube/potetos-for-everyone · skills/automate-me/SKILL.md · Create a personal mode skill from recurring workflow patterns in available history. Use when the user wants their own…
theonlyfusioncube/potetos-for-everyone · skills/benchmark-checklist/SKILL.md · Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened)…
theonlyfusioncube/potetos-for-everyone · skills/blast-radius/SKILL.md · Prove what a small-looking change can affect before or after editing. Use for compatibility, caller, state, schema, or…
theonlyfusioncube/potetos-for-everyone · skills/bro/SKILL.md · Restate the last technical explanation in plain human language with minimal jargon. Use when the user asks for a…
theonlyfusioncube/potetos-for-everyone · skills/correct/SKILL.md · Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types…
theonlyfusioncube/potetos-for-everyone · skills/create-formal-verification-skill/SKILL.md · Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in…
theonlyfusioncube/potetos-for-everyone · skills/create-verification-skill/SKILL.md · Generate a project-local verification skill that drives the real app and captures evidence. Use when setting up…
cursor/plugins · pstack/skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
cursor/plugins · harness/pstack/claude-code/skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
michael-denyer/pstack-claude · plugins/pstack/skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
backnotprop/pstack · skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
bastani-inc/atomic · packages/workflows/skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
j-star-films-studios/vibecode-protocol-suite · assets/.agent/skills/code-intelligence/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
creedants/pstack-t3 · skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
creedants/pstack-t3 · t3/overrides/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
