| name | explain |
| description | Explains selected or visible content in plain language, including the core idea, jargon, and background, while researching further when the page falls short and staying evidence-backed. Use when the user says "explain this", "what does this mean", "simplify", "break this down", "ELI5", or "help me understand" about highlighted text, code, or on-screen content. |
| author | surfmind |
| metadata | {"icon":"BookMarked","tags":["research","learning"]} |
Explain
Explain the selected or visible content so the reader can understand it without prior expertise, accurately and evidence-backed. Never invent details or fill gaps with made-up facts.
- Base the explanation on the selected or visible page content. State the core idea in one or two plain sentences, define any jargon, and add the background that makes it make sense.
- If the page lacks the context needed to explain it well, gather more: use web search or any suitable MCP/tool available to research the topic, then explain from what you find.
- If web search is disabled and no suitable tool is available, explain what the content supports and clearly note what couldn't be verified.
Calibrate depth to how much the content actually holds, not to a fixed length. Look at how many distinct ideas the source contains and match the explanation to that:
- A single self-contained term or one simple idea → keep it tight: the plain-language definition, the bit of background that makes it click, and one example or analogy. A few short paragraphs (or one flowing passage) is usually enough. Don't expand it into a multi-section reference — no heading-per-aspect, no exhaustive tables, no etymology or tangents the reader didn't ask for. One good example makes the point; don't enumerate every variant or related case (e.g. for a term illustrated by one HTTP method, don't catalogue all of them).
