Anthropic's /eli5 skill: two lines of instruction, one HTML file, no room for precision

The whole skill is two lines. The body that actually drives the model tells it to explain like someone who knows nothing about the topic, using an HTML artifact with big pictures and few words, then hands it `$ARGUMENTS` ^[7]. The `description` field, the part that decides when the skill fires, still says "explain a topic like I'm a 5 year old" ^[8]. dev.to reads that gap as deliberate: aiming at a literal five-year-old's vocabulary degrades accuracy, so the operative instruction was retuned toward stripping assumed background instead ^[20]. Practical effect for anyone reviewing installed plugins before letting them near customer-facing work: the field you read in the metadata is not the field that runs.

The gap between the two also shows up in output quality. Left alone, the skill sometimes produces fewer diagrams than you want ^[1]. The prompt dev.to used to get a usable RAG explainer specified at least three SVG diagrams and spelled out the flow to draw as a flowchart with arrows ^[2]. That prompt is longer and more prescriptive than the skill's own instruction, which means the constraint doing the work is supplied by the caller, not the skill ^[16].

Look at what came back. The four steps are gather documents, chop them into pieces, find similar chunks, read and answer, each with an emoji and a short phrase, sized to fit one screen ^[3]. None of those four steps names an embedding model or any ranking step ^[17]. dev.to is candid about this: the output is an entry point to what the mechanism even is, not a technically precise spec ^[13], and the skill optimises for getting the idea across over being correct ^[14]. For a new team member in week one that trade is right ^[15]. For anything where the omitted term is the operative one, the format has already thrown away the answer before you read it.

One more thing worth pinning. The plugin installs as version 1.0.0 at user scope ^[11], and dev.to notes its description of behaviour is current only as of August 2026 because Claude Code changes often ^[4]. So the same `/eli5` command run months apart is not guaranteed to yield the same explainer of the same system ^[18]. The artifact is durable, being a standalone HTML file ^[6]; the generator behind it is not pinned to anything you control. If these files end up in an onboarding folder, they are snapshots of a moving prompt, and nothing in the file says so.

The licensing is the cleanest part of the story: MIT, free, with Claude Code usage still billed under whatever plan you already have ^[9]. The cost is not the plugin. It is the review time nobody budgets for a document that was designed to be incomplete.