show-me
Skill1 starsChanged 19 days agoMITView on GitHub
Show the current topic instead of explaining it. "/show-me" draws the smallest picture in the chat, and a page if it needs a real diagram. "/show-me sheet" or "/show-me share" builds one HTML sheet of lettered panels, to open or publish. "/show-me flow" maps what was built as a user flow: screens, decisions, error paths and review marks.
79 other projects use a version of this.
Adopted by
Most recently taken up by
- waltyou/skillstheir own version, first seen Nov 8, 2026
- n1kben/agentstheir own version, first seen Nov 8, 2026
- Mharbulous/probanda-devtheir own version, first seen Nov 8, 2026
- ninondev/show-metheir own version, first seen Nov 8, 2026
- timmo001/skillstheir own version, first seen Nov 7, 2026
- MatthewYe/autopilot-toolkittheir own version, first seen Nov 7, 2026
Used with
Projects with it also use maintain-formal-verification-skill, create-formal-verification-skill and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
TheOnlyFusionCubeSkillmaintain-formal-verification-skill
Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, \"is the model still true to the code\", or after merges and refactors that touched verified code without rechecking it.
Also in 4 projects that use this
- TheOnlyFusionCubeSkill
create-formal-verification-skill
Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in any language, with whichever verification tool fits. Use for /create-formal-verification-skill, \"model-check this race\", \"prove this invariant\", or when concurrency, retries, state machines, parsers, or unsafe code need more than tests.
Also in 4 projects that use this
AnthropicSkilleli5
Explain a topic like I'm a 5 year old. Use when the user types /eli5 <topic> or asks for a dead-simple picture explainer of how something works.
Also in 10 projects that use this
drafaelSkillin-your-own-words
Restate the user's goals and the problem they are trying to solve to check understanding. Manual invocation only; use when the user explicitly invokes in-your-own-words or requests this understanding check. Do not solve the task or rewrite the assistant's last answer.
Also in 4 projects that use this
jaydubya818Skillcreate-verification-skill
Use when a repository needs a repeatable driver that proves real UI, CLI, or service behavior.
Also in 8 projects that use this
- jaydubya818Skill
maintain-verification-skill
Use when a project's verification driver or feature map may be stale.
Also in 7 projects that use this
- +1 more from jaydubya818
Other versions79 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 79
- withcoral/coral★ 4.9ksame name
- deadlock-mod-manager/deadlock-mod-manager★ 584same name
- kv0906/pm-kit★ 138same name
- Dimon94/dverity★ 107same name
- Dimon94/skills★ 107same name
- charlie947/show-me★ 70same name
- kv0906/cc-skills★ 42same name
- Melvynx/ai-maxxing-skills★ 32same name
- IgorGanapolsky/ThumbGate★ 30same name
- Integralist/agent-skills★ 23same name
69 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- broooooSkill
- did-we-break-itSkill
- finish-the-prSkill
- fix-it-properlySkill
- just-tell-meSkill
- lets-build-pyramidsSkill
- next-time-fasterSkill
- no-added-commentsSkill
- onmywatchSkill
- plan-the-big-oneSkill
- sharpenSkill
- statechartSkill
- talk-is-cheapSkill
- trust-issuesSkill
- trust-me-broSkill
- walk-me-throughSkill
- you-get-meSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 73 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
If the first word is sheet, flow or share, it picks the page and the rest is the topic.
- Distinctive: line 18
Stop at the first level that makes it clear.
- Distinctive: line 41
Keep only what answers the question.
- Distinctive: line 45
Write about 80% of the way to ASD-STE100 Simplified Technical English.
- Distinctive: line 51
Every line, mark and colour must carry meaning.
“Common” is measured: kept by at least 6 in 10 of the 73 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
show-me
Show the idea. The picture comes first.
Arguments: $ARGUMENTS
If the first word is sheet, flow or share, it picks the page and the rest is the topic. Otherwise the arguments are the topic, or the current conversation if there are none, and you pick the level.
Pick the level
Stop at the first level that makes it clear. Read only the file your level names, from this skill's folder.
| Level | Use when | Form | Read next |
| Words | One fact or one rule | Two or three sentences | Nothing |
| Text picture | Logic, one call path, files, a change | A code block in the chat | Nothing |
| Small diagram | Up to 4 parts in one line | A text box diagram in a code block | Nothing |
| Sheet | 5 or more parts talking, branches or loops, a comparison, or sheet or share | One HTML page of lettered panels, opened for the reader | playbooks/sheet.md |
| Walkthrough | How something works and why, with more than one view | One HTML page with tabs and guided steps | playbooks/walkthrough.md |
| Flow | A user journey through UI states, or flow | One HTML map of screens and decisions | playbooks/flow.md |
Never put Mermaid, SVG or HTML in the chat. The terminal shows them as source code, not as a picture. If a text picture does not read correctly in a monospace code block, build a page.
Text pictures
Pick the one shape that fits. Use a second only if it shows something the first cannot.
- Logic as pseudocode:
on(save) / if unchanged / return cached. - Runtime flow as a call tree, indented by who calls whom.
- UI as a component tree, with the state and the file of each part.
- Ownership as a shallow file tree with one comment per folder.
- A change as a
diffof any shape above:+new,-gone.
Keep only what answers the question.
Writing
Write about 80% of the way to ASD-STE100 Simplified Technical English. Code, quotes and UI labels stay as they are.
- One topic per sentence. At most 20 words for an instruction, 25 for a description.
- Active voice, simple tenses, short common words. No idioms, metaphors or jokes.
- One name for one thing. Names from the code stay exact.
Every line, mark and colour must carry meaning. Never draw boxes for decoration.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.