agentleFS
Sign inStart free
IgorGanapolskyIgorGanapolsky/ThumbGate/.agents/skills/show-me/SKILL.md

show-me

Skill29 starsChanged 7 months agoMITView on GitHub

Answer architecture / control-flow questions with a compact visual format (component tree, call stack, mermaid, annotated diff) instead of prose walls. House steal of ExplainX /show-me FORMAT — not affiliated. Slash: /show-me.

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 66 edited versions we read keep these.

  • 0

    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
  1. Very specific:

    Prefer these labels when drawing: PreToolUse, gate-check, session-lease, lesson-retrieval, graphify, Trunk, Railway /health, …

    line 34

“Common” is measured: kept by at least 6 in 10 of the 66 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/show-me — draw, don't ramble

Inspired by ExplainX trending #9 (score 87): The /show-me Skill — the format menu is the product. The model can already draw; the skill makes format selection deterministic.

When

Architecture, PreToolUse/gate flow, adapter wiring, "what calls what", PR blast radius, session lease ownership. Prefer this over a paragraph dump.

Format menu (pick one)

FormatWhen it wins
Component / module treeWho owns which state or gate
Call stackOrchestration order
File layoutDirectory + one-line responsibility
Mermaid sequenceMulti-party over time (agent → hook → API)
Mermaid stateModes + transitions (lease, merge, deploy)
Annotated diffWhat changed at structure level
PseudocodeBranching logic without language noise

ThumbGate vocabulary (house version)

Prefer these labels when drawing: PreToolUse, gate-check, session-lease, lesson-retrieval, graphify, Trunk, Railway /health, containerTag/scope.

Never

  • Diagram slop on non-visual questions
  • Install humanlayer/skills blindly — this file is the house skill
  • Claim affiliation with ExplainX or HumanLayer
  • Replace graphify path/query when graphify-out/graph.json exists — fuse both

Companion

npm run explainx:trending -- --fixture tests/fixtures/explainx-trending-rsc-snippet.html
.graphify-venv/bin/graphify path "<A>" "<B>"   # when graph exists

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free