菜单
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".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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".
Generate a structured summary of everything explained in this session and save a concept index for future sessions. Trigger when the user says "/eli-recap", "session summary", "what did we cover", "summarize the session", "what did I learn today", or "recap".
| name | eli-brief |
| description | 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". |
Exactly 3 sentences. Safe to paste into Slack, email, or a board deck.
[What it is] — one concrete analogy, zero jargon.
[Why it matters] — the real-world impact or user benefit.
[What to watch for / what action is needed] — the one thing they should know or decide.
Input: /eli-brief rate limiting
Output:
Rate limiting is like a bouncer at a door who lets in only a set number of people per minute. It stops one bad actor from overwhelming a system and slowing it down for everyone else. Right now our API allows 100 requests per minute per user — if that's causing issues, we can raise or lower it.