use this when opening or rewriting a pull request description, or when the user needs a visual explanation of code shape, flow, or structure — keep PR bodies easy to scan with the smallest clear diagram.
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
# show-me
Source: adapted from [HumanLayer, show-me](https://github.com/humanlayer/skills/blob/3c2629142c5d437428269b1b722b08c0b87f574d/plugins/show-me/skills/show-me/SKILL.md). [Dexter Horthy's launch article](https://www.humanlayer.com/blog/show-me-skill) credits Dillon Mulroy and Matt Pocock as influences. MIT; see [third-party notices](../../../THIRD_PARTY_NOTICES.md).
Help the reader understand the change visually. Skip the preamble. Keep prose brief. Pick the **smallest** view that makes the key point clear. Prefer putting these visuals **in the PR body** next to the short text they support.
## When opening a PR
1. Write Why / What / How to verify in short prose (or fill the repo template).
2. Add one or more show-me blocks so a reviewer can scan shape without reading the whole diff first: a file-tree diff, a call-tree diff, a component-tree diff, a state/control-flow diff, or a Mermaid sequence — whichever matches the change.
3. Do not dump every format. One or two well-chosen views beat a collage.
4. Every claim in a visual must match the real diff. No invented paths or symbols.
5. Redact secrets. Prefer public-safe labels.
## Toolbox
…
The line at the top of this page pins the label git:20260917.c6ed2fc, 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_racr662gw2pf5yiq
GET https://markdownregistry.com/api/v1/resolve?ref=coolxeo/grok-bot-skills/show-me
GET https://markdownregistry.com/api/v1/blob/7e5a96a6cbb81fdf84a431efcfb56c4fb107fbe111a5488ab43bd94dc302a3a1
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.
coolxeo/grok-bot-skills · skills/bots/design-a-grok-bot/SKILL.md · Use this when designing or creating a new Grok Bot. Ask a few preference questions, write a tight persona, CreateAgent…
coolxeo/grok-bot-skills · skills/bots/overheard-setup/SKILL.md · First-run watch-list interview. Also use when the user wants to reconfigure names, brands, URLs, or sources.
coolxeo/grok-bot-skills · skills/bots/routine-healthcheck/SKILL.md · Use when auditing Grok Bot routines for token waste, offering a fleet checkup after template import, deciding cadence…
coolxeo/grok-bot-skills · skills/bots/transcript-healthcheck/SKILL.md · Use when auditing Grok Bot fleet transcripts for user friction, proposing new skills/bots/routines from repeated…
coolxeo/grok-bot-skills · skills/design/diagram-design/SKILL.md · use this when creating explainer diagrams (architecture, sequence, process, cards for posts) as HTML/SVG/PNG so they…
coolxeo/grok-bot-skills · skills/engineering/engineering-playbook/SKILL.md · Standing principles for delegating code to cloud agents and supervising PRs to merge. Use on every ship or watch.
coolxeo/grok-bot-skills · skills/images/chatgpt-images-browser-playbook/SKILL.md · Use when generating stills on chatgpt.com with a signed-in browser session — Images UI only, one still per dispatch, no…
coolxeo/grok-bot-skills · skills/seo/aeo-geo-site/SKILL.md · use this when building or updating a website for SEO plus AEO/GEO (AI assistants, ChatGPT, Copilot, Gemini) so pages…
coolxeo/grok-bot-skills · skills/seo/exact-match-intent-seo/SKILL.md · use this when choosing domains, URL slugs, titles, or H1s for SEO — Exact Match Domain (EMD) lessons and the safer…
coolxeo/grok-bot-skills · skills/writing/coach/SKILL.md · Use this when a draft needs a structural read before line-edit — thesis, arc, and teach test first, style second.
coolxeo/grok-bot-skills · skills/writing/draft/SKILL.md · Use this when writing or expanding an article section by section. Never generate a full article in one shot.
bastani-inc/atomic · packages/workflows/skills/show-me/SKILL.md · Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML…
bendrucker/claude · user/skills/show-me/SKILL.md · Explain the current topic or a proposed design visually with types and signatures, pseudocode, a call tree, a component…
vanducng/skills · skills/show-me/SKILL.md · Explain the current topic with the cheapest in-chat visual. Skip the preamble and pick the smallest view that makes the…
ahgraber/skills · skills/show-me/SKILL.md · Use when the user needs to see something to answer the current question — a sketch of logic, runtime flow, UI…
ucsandman/claude-skills · show-me/SKILL.md · Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML…
transitive-bullshit/skills · skills/show-me/SKILL.md · Explain a topic visually with a concise diagram or focused HTML artifact. Use when a visual materially improves…
transitive-bullshit/skills · provenance/upstream/show-me/SKILL.md · Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML…
