Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tobihagemann/explain-this
Explain whatever the user is pointing at right now in plain language: a pending question, a piece of code, an error, a command output, or an artifact like a plan or findings report.
Passed 17 of 21 test cases with the skill, and 15 of 21 without it.
and 3 more in the full report
5 fixed13 passed either way1 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
The assistant just presented me with a choice on how to refactor our auth module. Can you explain this decision to me? Restate the core question simply, outline each of the listed options along with their concrete impact, pros and cons, and clarify which scenario each option is best suited for.
| Checked | Without skill | With skill |
|---|---|---|
| The response states that the subject to explain cannot be identified. | Missed | Passed |
| The response stops without providing speculative refactoring options. | Missed | Passed |
The instructions your model reads when the skill loads.
Take whatever the user is pointing at and translate it into plain language. "This" is usually the most recent assistant output or something pasted as an argument: a multi-option prompt, a free-form question, a code block, an error, a command output, or an artifact like a plan, findings report, or diff.
Pick the subject in priority order:
Read whatever makes the explanation concrete, no more:
SKILL.md when a skill-specific question is being askedgit status and git diff --stat when the subject involves staged or unstaged changesThe reader is an experienced developer who may not be fluent in every tech stack or acronym but doesn't need concepts from first principles. Skip ELI5. Use plain language; strip skill-internal jargon, or define it inline when the jargon is what the user needs explained (for example, "P1 peer" becomes "priority 1 finding from the peer reviewer").
Go beyond "what this does" and surface the trade-offs: pros and cons per choice, benefits and costs, whether the thing reads as clean and elegant or redundant and overcomplicated. Be honest about red flags; be honest about solid work.
Shape the output to match the subject. Use the branch that applies; drop the rest.
Question with discrete options — restate the question plainly, then enumerate options using this template:
**What you're being asked:** <plain-language restatement>
### Your Options
**1. <label as shown>** — <concrete effect: files changed, next step, what is lost>
- **Pros:** <what you gain>
- **Cons:** <what it costs>
**2. <label>** — <concrete effect>
test cases passed, vs 15 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.