菜单
Tests the user's understanding of the most recent eli5 explanation. Trigger when the user says "/eli-quiz", "test me", "quiz me", "check my understanding", "did I get it?", "make sure I understand", or "quiz me on that".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate a 3-sentence plain-language summary safe to send to executives or clients. Trigger when the user says "/eli-brief", "executive summary", "tl;dr for my boss", "explain briefly for non-technical", "3 sentences", "send to my manager", "non-technical summary", or "boardroom version".
Generate a plain-language commit message from staged changes. Trigger when the user says "/eli-commit", "write a commit message", "commit message eli5", "explain these changes for git", "what should my commit say", or "help me write a commit".
Compare two concepts side by side at the current eli5 level. Trigger when the user says "/eli-compare", "compare X vs Y", "what's the difference between X and Y", "eli5 X versus Y", "X vs Y explained simply", or "help me understand X and Y".
Generates a plain-language glossary (ELI5.md) for the current codebase. Trigger when the user says "/eli-doc", "generate eli5 docs", "make a plain-language glossary", "explain this codebase simply", "create eli5 documentation", or "document this for beginners".
Generate a plain-language PR description from the current git diff. Trigger when the user says "/eli-pr", "write a PR description", "write this PR simply", "PR description for non-technical", "explain this PR to my manager", or "generate PR desc".
Show what you need to understand before tackling a concept — a learning path, not just a definition. Trigger when the user says "/eli-prereqs", "what do I need to know first", "prerequisites for X", "learning path for X", "where do I start with X", "what should I learn before X", or "I want to understand X from scratch".
| name | eli-quiz |
| description | Tests the user's understanding of the most recent eli5 explanation. Trigger when the user says "/eli-quiz", "test me", "quiz me", "check my understanding", "did I get it?", "make sure I understand", or "quiz me on that". |
Test whether the last explanation landed. Ask questions at the current eli5 level.
Check current level:
cat .claude/eli5-state.json 2>/dev/null || echo "none"
If no level found, default to eli5.
Identify the most recent concept explained in eli5 mode from the conversation.
Write 2–3 questions calibrated to the current level:
eli5 / eli-kid: Fill-in-the-blank or "what is this like?" questions. Example: "A database is like a giant ___. What goes in the blanks?"
eli-teen: "Real-world scenario" questions. Example: "If OAuth is a backstage wristband, what happens when it expires?"
eli-adult / eli-expert: "Apply it" questions. Example: "Your team is hitting slow API responses. Which analogy from today would you use to explain caching to your manager?"
Ask ONE question at a time. Wait for the answer before giving the next.
For each answer, give feedback in the current eli5 level's style:
After all questions, give a brief summary: "You got [N/3]. [level-appropriate encouragement]."
Stay in eli5 mode throughout the quiz. Questions, hints, and feedback all follow
the current level's rules from ~/.claude/skills/eli5-mode/references/core-rules.md.