AGENT SKILL

eli5

Explain any topic in the simplest possible terms using analogies and everyday examples. Use when the user says "explain like I'm 5", "eli5", "explain simply", "dumb it down", or "explain in simple terms".

License 许可
MIT
所属仓库
drn/dots
最近更新
2026-11-12
Stars
★ 23
Forks
4

01 前言 Front Matter

name
eli5
description
Explain any topic in the simplest possible terms using analogies and everyday examples. Use when the user says "explain like I'm 5", "eli5", "explain simply", "dumb it down", or "explain in simple terms".

03 SKILL.md 正文

Explain Like I'm 5

Break down a topic so a 5-year-old could understand it.

Arguments

  • $ARGUMENTS - The topic, concept, code, error message, or architecture decision to explain

Instructions

Step 1: Identify the topic

Read $ARGUMENTS. If empty, ask the user what they want explained and stop.

The topic can be anything:

  • A programming concept (e.g., "recursion", "dependency injection")
  • A piece of code (read the file or selection first)
  • An error message or stack trace
  • An architecture decision or system design
  • A non-technical concept

If the topic references a file or code, read it before explaining.

Step 2: Explain it using the ADEPT pattern

Structure your explanation in this order:

  1. Core idea first. State what it is in one plain sentence. No jargon, no acronyms unless you define them immediately. This is the "headline" -- if the reader stops here, they still learned something.

  2. Analogy. Connect the concept to something from everyday life -- toys, food, playgrounds, animals, building blocks, a library, a kitchen. Pick an analogy that maps well to the actual mechanics, not just the surface.

  3. Diagram (when visual). If the concept has structure, flow, or relationships, include a short ASCII diagram. Keep it under 10 lines. Skip this for purely abstract concepts where a diagram would not help.

  4. Example. Walk through one concrete, minimal example. For code concepts, show 3-5 lines of real code with a one-line comment. For non-code topics, give a specific scenario.

  5. Plain-English summary. One sentence a child could repeat back. Connect the analogy to the real thing: "So [analogy] is like [real thing] because..."

Rules:

  • Use short sentences. Active voice. Simple words.
  • Do not hedge, qualify, or add caveats. Be confident and direct.
  • Accuracy matters but simplicity wins -- leave out details that do not help understanding.
  • If the topic has multiple parts, build up layer by layer. Start with the simplest piece and add complexity one step at a time.
  • Maximum 2-3 short paragraphs of prose per section. Brevity is the goal.

Step 3: Offer to go deeper

After the explanation, offer: "Want me to go deeper on any part of this, or see more examples?"

04 同仓库更多 Skills

drn
drn/dots

batch-pr-review

Review a batch of pull requests together, describe every change in plain language, and build a private Claude artifact that eases human review, with a severity-tagged and verified findings list. Use when asked to review several PRs, a stack of PRs, PRs listed in a Slack thread or message, or to summarize a batch of PRs for a reviewer.

邮件与沟通
★ 23
drn
drn/dots

plannotator-setup-goal

Create reviewed Codex goal setup packages for long-running /goal work. Use when the user wants to turn an idea, backlog, project mission, or vague objective into durable goal files under a project goals slug folder, with Plannotator review gates for brief, narrative plan with acceptance criteria, verification, blockers, and the final /goal prompt.

Skill与智能体开发
★ 23
drn
drn/dots

plannotator-annotate

Open Plannotator's annotation UI for a markdown file, converted HTML file, URL, or folder and then respond to the returned annotations.

★ 23
drn
drn/dots

write-skill

Create or improve a Claude Code skill/slash command with best practices for structure, dynamic context, and safety. Use for creating new skills, improving existing ones, or learning skill authoring.

Skill与智能体开发
★ 23
drn
drn/dots

wrapup

End-of-session checklist that detects loose ends — uncommitted changes, unmerged branches, learnings to capture, handoffs needed — and routes to the right skills. Use for session closeout, wrapping up, end of day, or "anything else to capture".

★ 23
drn
drn/dots

tts

Read text aloud using text-to-speech. Use when the user says "speak to me", "read to me", "read this aloud", "say this", "speak the summary", or asks to hear something spoken.

★ 23