A HumanLayer közzétette a show-me nevű bővítményt, amely arra utasítja a kódoló AI-ügynököket, hogy a többszörös bekezdésekből álló magyarázatok helyett tömör vizuális elemekkel válaszoljanak. A fejlesztők így felesleges szövegek helyett pszeudokódokat, hívási fákat, komponensfákat vagy Mermaid-diagramokat kapnak a kód felépítéséről.
Az eszköz a skills CLI felületen keresztül telepíthető, és a `/show-me` parancssori paranccsal hívható meg. Mivel a bővítmény logikája egyetlen egyszerű `SKILL.md` fájlban található utasításrendszer, a felhasználók testre szabhatják a formátumokat a HumanLayer nyílt forráskódú bővítménytárában.
A rendszer abban is segít, hogy a modell csak a lényeges összefüggéseket mutassa meg: megadja, mikor érdemes teljes kódblokkot vagy egy különálló, fókuszált HTML-oldalt generálni a jobb átláthatóság érdekében.
Az eredeti szöveg (The Art of Simplicity (daily.dev))
Coding agents are good at explaining things. They are also good at explaining them in five verbose paragraphs when a ten-line tree would have done the job. You would almost think that output tokens are free!
Recently I came across the show-me skill from HumanLayer. It’s a small skill with one purpose: when you ask your agent to explain something, it answers with a visual representation instead of a wall of text.
The whole skill is a short set of instructions. It tells the agent to skip the preamble, keep the prose brief and pick the smallest view that makes the point clear.
Sounds simple? Because the idea is indeed. For each kind of explanation, the skill names the view to use:
Here is what that looks like in practice. A call tree for a form submit:
And a shallow file tree to explain who owns what:
Nothing fancy. But compare that with the paragraph you would normally get back.
The skill can be installed with the skills CLI:
After that you invoke it with a slash command like any other skill:
As an architect I have to read a lot of code. Most of the time when I’m reviewing code changes, I’m not looking for an explanation. I’m looking for the shape of something: who calls whom, which module owns the state, where a refactor will touch. That is exactly what trees and sequence diagrams are good at, and prose is not.
The skill also forces the agent to be selective. You don’t get a diagram of everything, just the one that answers your question.
The skill also covers when to show a full code block instead of a fragment: when most of it is new, when leaving out context would hide ownership or order, or when you need a target shape you can copy. For larger explanations it can also produce a focused HTML page, which the agent opens for you.
Remark: The skill is plain instructions, nothing more. If you disagree with one of its choices (say you prefer ASCII over Mermaid), you can read the SKILL.md and adjust it for your own setup.
If you regularly ask your agent to explain unfamiliar code, yes. It costs one command to install and it changes the format of every answer you ask for with /show-me.
