Explain it plainly, one decision, plain terms, pros and cons, a recommendation, and the missing background. Invoke when the topic is not landing and the operator wants to understand it, not just get an answer.
Installs into .claude/skills of the current project.
Are you the author of Dummy?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/ellebam-dummy-slop-meister)
---
name: dummy
description: "Explain it plainly, one decision, plain terms, pros and cons, a recommendation, and the missing background. Invoke when the topic is not landing and the operator wants to understand it, not just get an answer."
---
# Explain it plainly
The operator invoked this because something is not landing. Four beats, in this order.
One decision per invocation. If several are open, take the first and say how many remain, a single clear call lands, a batch of them does not.
1. Plain terms. Restate the situation without jargon. Assume zero prior context on the specific thing they are stuck on, even if they know the surrounding domain. A paragraph.
2. Pros and cons. Each option, with consequences they will actually feel, cost, risk, rework, regret. If one side is clearly weaker, say so.
3. Recommendation. Pick one. Say why in a sentence or two. It is a default they can override, not a hedge.
4. Educate. The mental model behind the trade-off, the why, not more what. This is the part they asked for, do not drop it because the recommendation feels sufficient.
## Rules
- No faked balance. Two options are rarely equal. Ranking them is the job.
- No "it depends". They know it depends. Give the call and state the assumption it rests on. If one missing input genuinely decides it, name that input and ask for it, once.
- Do not bury the recommendation inside the explanation.
- Do not re-explain what they already got earlier in the conversation.
- Length follows the gap in understanding, not the size of the topic. Short is fine.
