Skip to content
Back to skills

Eli40

ASecurity

Re-explains concepts at a "knows the basics" level — strips jargon, uses analogies, and assumes broad general knowledge without domain expertise. Use when the user invokes /eli40 to request a simpler explanation of the previous message, or /eli40 <topic> to get an accessible explanation of a specific topic. Like ELI5 but calibrated for an adult generalist.

  • 9 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 27, 2026
data-aigogitapidatabasefrontend

Works with

  • api

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add isvlasov/rageatc-oss --skill eli40 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Eli40?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Eli40
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/isvlasov-eli40/badge)](https://www.skillsdirectory.com/skills/isvlasov-eli40)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: eli40
description: Re-explains concepts at a "knows the basics" level — strips jargon, uses analogies, and assumes broad general knowledge without domain expertise. Use when the user invokes /eli40 to request a simpler explanation of the previous message, or /eli40 <topic> to get an accessible explanation of a specific topic. Like ELI5 but calibrated for an adult generalist.
---

# ELI40

## Purpose

The user has asked you to explain something more simply. They are an intelligent adult with broad general knowledge across many domains, but they lack expert depth in the specific area being discussed. Your job is to re-explain clearly without assuming specialist knowledge.

## Behaviour

### Without argument

Re-explain your most recent message or suggestion. Cover the same ground but:

1. **Replace jargon** with plain language, or define it inline on first use
2. **Use analogies** to familiar concepts where they genuinely clarify
3. **Explain the "why"** — don't just state facts, connect them to reasons
4. **Keep structure** — use the same logical flow, just at a more accessible level
5. **Be honest about simplification** — if you're glossing over important nuance, say so briefly

### With argument (e.g. `/eli40 HTMX frontend`)

Explain the given topic from scratch at the same accessible level. Follow the same principles above.

## Calibration

**Do:**
- Assume they understand: variables, APIs, databases, git, basic networking, how the web works, general programming concepts
- Assume they do NOT know: framework-specific internals, protocol details, academic CS terminology, niche architectural patterns
- Use concrete examples over abstract definitions
- Keep it concise — simpler doesn't mean longer

**Don't:**
- Patronise or over-simplify ("so basically, a computer is like a brain...")
- Add unnecessary caveats or hedging
- Turn it into a lecture — match the length of the original explanation roughly
- Use "basically" or "simply put" as crutches

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.