how SKILL.md skillA

how from yeachan-heo/oh-my-claudecode is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add yeachan-heo/oh-my-claudecode/how@git:20261108.ac1df7f

Pins git:20261108.ac1df7f in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
yeachan-heo/oh-my-claudecode
Path
skills/how/SKILL.md
Versions recorded
1
Latest version
git:20261108.ac1df7f, committed Nov 8, 2026
Size
1,812 bytes
Repository stars
40,827
License
MIT

Walk through how a subsystem works — a fast explorer maps the territory, an explainer writes the layered walkthrough. Use for "how does X work", onboarding on unfamiliar code, or before changing a subsystem you cannot yet explain.

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

Explain how a subsystem works, layered so each layer stands alone. Two roles,
two passes:

1. **Explore** (read-only, fast): dispatch `oh-my-claudecode:explore` to map
   the subsystem — entry points, main flows, data shapes, state, external
   calls, and the files that own each. Explorer returns a map with file:line
   citations, not prose.
2. **Explain** (lead): write the walkthrough from the map, reading the cited
   code yourself where the claim is load-bearing.

## Output shape

- **One paragraph**: what the subsystem does and for whom, no jargon.
- **Walkthrough**: the main path end to end, step by step, each step citing
  `file:line`. Diverge into how errors and retries are handled at the point
  they occur.
- **Edge cases and invariants**: what must stay true for the walkthrough to
  hold, and what happens when it does not.
- **Boundaries**: what this subsystem deliberately does not do.

## Rules

- Every behavioral claim cites code you or the explorer read this session;
  an uncited claim is labeled a guess.
- The walkthrough explains the code as it is, not as it should be; design
  critique belongs to `why` and `review`.
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_lhiftix4yy4fyijo/6496411b978316a4beb4cbf2c267022167566fbbc27d74807928f5de22b9192f.json

Then /plugin install how@markdownregistry-lhiftix4yy4fyijo in Claude Code. It installs git:20261108.ac1df7f, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add yeachan-heo/oh-my-claudecode/how@sha256:6496411b978316a4

The line at the top of this page pins the label git:20261108.ac1df7f, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_lhiftix4yy4fyijo.svg)](https://markdownregistry.com/a/art_lhiftix4yy4fyijo)

6 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in yeachan-heo/oh-my-claudecode/how since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of how from somewhere else? Ask it: where did my how come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 1 version of this file, committed on Nov 8, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261108.ac1df7f latest2026-11-08 ac1df7f 1,812 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (1812 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

GitHub

yeachan-heo/oh-my-claudecode · 40,827 stars · license MIT · pushed 2026-11-14 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_lhiftix4yy4fyijo
GET https://markdownregistry.com/api/v1/resolve?ref=yeachan-heo/oh-my-claudecode/how
GET https://markdownregistry.com/api/v1/blob/6496411b978316a4beb4cbf2c267022167566fbbc27d74807928f5de22b9192f

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 yeachan-heo/oh-my-claudecode

CLAUDE.md@.github CLAUDE.md file
yeachan-heo/oh-my-claudecode · .github/CLAUDE.md
git:20261111.453d3de · audit A · 40,827 stars
AGENTS.md AGENTS.md file
yeachan-heo/oh-my-claudecode · AGENTS.md
git:20261013.dba5ef3 · audit A · 40,827 stars
CLAUDE.md CLAUDE.md file
yeachan-heo/oh-my-claudecode · CLAUDE.md
git:20261111.453d3de · audit A · 40,827 stars
AGENTS.md@docs AGENTS.md file
yeachan-heo/oh-my-claudecode · docs/AGENTS.md
git:20260311.fc226e7 · audit A · 40,827 stars
CLAUDE.md@docs CLAUDE.md file
yeachan-heo/oh-my-claudecode · docs/CLAUDE.md
git:20261111.7d214ca · audit A · 40,827 stars
AGENTS.md@skills AGENTS.md file
yeachan-heo/oh-my-claudecode · skills/AGENTS.md
git:20261108.fbca6c4 · audit A · 40,827 stars
agent-doc-discipline SKILL.md skill
yeachan-heo/oh-my-claudecode · skills/agent-doc-discipline/SKILL.md · Writing-time discipline for documents agents consume (the five surfaces, specs, tickets, .omc/skills/) — every rule…
git:20261009.3e432c2 · audit A · 40,827 stars
ai-slop-cleaner SKILL.md skill
yeachan-heo/oh-my-claudecode · skills/ai-slop-cleaner/SKILL.md · Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
git:20261108.ac1df7f · audit A · 40,827 stars
architect SKILL.md skill
yeachan-heo/oh-my-claudecode · skills/architect/SKILL.md · Settle types and module shape before cross-boundary code — competing designs explored in parallel, compared on API…
git:20261108.ac1df7f · audit A · 40,827 stars
architecture-survey SKILL.md skill
yeachan-heo/oh-my-claudecode · skills/architecture-survey/SKILL.md · Periodic architecture survey — walks the module graph and reports ranked deepening candidates (shallow modules…
git:20260913.629d16f · audit A · 40,827 stars
arena SKILL.md skill
yeachan-heo/oh-my-claudecode · skills/arena/SKILL.md · Run N parallel candidates at one brief and synthesize: rubric-first framing, isolated fan-out, a cross-judge on a…
git:20261108.ac1df7f · audit A · 40,827 stars
ask-navigator SKILL.md skill
yeachan-heo/oh-my-claudecode · skills/ask-navigator/SKILL.md · Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision…
git:20261011.3d50d68 · audit A · 40,827 stars

Every file in yeachan-heo/oh-my-claudecode

Other files named how

how SKILL.md skill
cursor/plugins · pstack/skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
git:20261115.bf0c7cd · audit A · 16,411 stars
how SKILL.md skill
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…
git:20261115.bf0c7cd · audit A · 16,411 stars
how SKILL.md skill
nightly-labs/openbot · marketplace/production-catalog/bundles/pstack/skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
git:20261013.9e6954c · audit A · 8,361 stars
how SKILL.md skill
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…
git:20261104.e66f85f · audit A · 4,340 stars
how SKILL.md skill
backnotprop/pstack · skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
git:20261020.e44668c · audit A · 4,184 stars
how SKILL.md skill
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…
git:20260823.166e8d7 · audit A · 883 stars
how SKILL.md skill
asymmetric-al/core · .agents/skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
git:20261109.c998def · audit A · 370 stars
how SKILL.md skill
iap/pstack-hermes · skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
git:20261006.f7c5841 · audit A · 38 stars

Browse by kind, by grade A, or by owner.