[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BV0TV6KVMT7EVRSWJWQNPX":3,"skill-same:01M6BV0TV6KVMT7EVRSWJWQNPX":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M6BV0TV6KVMT7EVRSWJWQNPX","eli5",null,"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\".","drn\u002Fdots","drn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F885841?v=4","01M6BTZJR7B1RVQRJKP0S70DQS","Darren Cheng","01M6BTZJWXCK41P3Z50BV8KWD9",23,"MIT","https:\u002F\u002Fgithub.com\u002Fdrn\u002Fdots\u002Fblob\u002Fmaster\u002Fagents\u002Fskills\u002Feli5\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27],"examples","explain","terms","user","use","simple","it","down","when","2026-11-10 10:12:30",false,"---\nname: eli5\ndescription: 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\".\n---\n\n# Explain Like I'm 5\n\nBreak down a topic so a 5-year-old could understand it.\n\n## Arguments\n\n- `$ARGUMENTS` - The topic, concept, code, error message, or architecture decision to explain\n\n## Instructions\n\n### Step 1: Identify the topic\n\nRead `$ARGUMENTS`. If empty, ask the user what they want explained and stop.\n\nThe topic can be anything:\n- A programming concept (e.g., \"recursion\", \"dependency injection\")\n- A piece of code (read the file or selection first)\n- An error message or stack trace\n- An architecture decision or system design\n- A non-technical concept\n\nIf the topic references a file or code, read it before explaining.\n\n### Step 2: Explain it using the ADEPT pattern\n\nStructure your explanation in this order:\n\n1. **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.\n\n2. **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.\n\n3. **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.\n\n4. **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.\n\n5. **Plain-English summary.** One sentence a child could repeat back. Connect the analogy to the real thing: \"So [analogy] is like [real thing] because...\"\n\nRules:\n- Use short sentences. Active voice. Simple words.\n- Do not hedge, qualify, or add caveats. Be confident and direct.\n- Accuracy matters but simplicity wins -- leave out details that do not help understanding.\n- If the topic has multiple parts, build up layer by layer. Start with the simplest piece and add complexity one step at a time.\n- Maximum 2-3 short paragraphs of prose per section. Brevity is the goal.\n\n### Step 3: Offer to go deeper\n\nAfter the explanation, offer: \"Want me to go deeper on any part of this, or see more examples?\"\n","# Explain Like I'm 5\n\nBreak down a topic so a 5-year-old could understand it.\n\n## Arguments\n\n- `$ARGUMENTS` - The topic, concept, code, error message, or architecture decision to explain\n\n## Instructions\n\n### Step 1: Identify the topic\n\nRead `$ARGUMENTS`. If empty, ask the user what they want explained and stop.\n\nThe topic can be anything:\n- A programming concept (e.g., \"recursion\", \"dependency injection\")\n- A piece of code (read the file or selection first)\n- An error message or stack trace\n- An architecture decision or system design\n- A non-technical concept\n\nIf the topic references a file or code, read it before explaining.\n\n### Step 2: Explain it using the ADEPT pattern\n\nStructure your explanation in this order:\n\n1. **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.\n\n2. **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.\n\n3. **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.\n\n4. **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.\n\n5. **Plain-English summary.** One sentence a child could repeat back. Connect the analogy to the real thing: \"So [analogy] is like [real thing] because...\"\n\nRules:\n- Use short sentences. Active voice. Simple words.\n- Do not hedge, qualify, or add caveats. Be confident and direct.\n- Accuracy matters but simplicity wins -- leave out details that do not help understanding.\n- If the topic has multiple parts, build up layer by layer. Start with the simplest piece and add complexity one step at a time.\n- Maximum 2-3 short paragraphs of prose per section. Brevity is the goal.\n\n### Step 3: Offer to go deeper\n\nAfter the explanation, offer: \"Want me to go deeper on any part of this, or see more examples?\"\n",{"name":5,"description":7},"master","427f62a9fc82624977516767979411f885161ac5","agents\u002Fskills\u002Feli5",4,"https:\u002F\u002Fgithub.com\u002Fdrn\u002Fdots","https:\u002F\u002Fgithub.com\u002Fdrn","https:\u002F\u002Fdrn.dev","CTO & Co-Founder @thanx","2026-11-12 16:13:13",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add drn\u002Fdots --skill eli5",{"tool":48,"command":49},"bunx","bunx skills add drn\u002Fdots --skill eli5",{"tool":51,"command":52},"pnpm","pnpm dlx skills add drn\u002Fdots --skill eli5","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdrn\u002Fdots\u002Fblob\u002Fmaster\u002Fagents\u002Fskills\u002Feli5\u002FSKILL.md",true,[],[57,88,108,120,145,163],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":68,"publishedAt":28},"01M70KJSG2P5Y3N95MGSGKJ8VA","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.","https:\u002F\u002Fgithub.com\u002Fdrn\u002Fdots\u002Fblob\u002Fmaster\u002Fagents\u002Fskills\u002Fbatch-pr-review\u002FSKILL.md",[63],{"categoryNo":64,"categoryName":65,"taxonomyType":66,"taxonomyTypeDesc":67},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[69,70,71,72,73,74,27,75,76,77,78,79,80,81,82,83,84,85,86,87],"batch pr review","batch","pr","pr review","review","reviewer","parse","scripts","human","artifact","message","write","read","stack","gh pr","Bash","change","pull requests","slack",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":97,"publishedAt":28},"01M6BV2G3ZAS76C40S3YBY6R61","plannotator-setup-goal","Create reviewed Codex goal setup packages for long-running \u002Fgoal 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 \u002Fgoal prompt.","https:\u002F\u002Fgithub.com\u002Fdrn\u002Fdots\u002Fblob\u002Fmaster\u002Fagents\u002Fskills\u002Fplannotator-setup-goal\u002FSKILL.md",[94],{"categoryNo":95,"categoryName":96,"taxonomyType":66,"taxonomyTypeDesc":67},"01JBSEEDCAT000000000000023","Skill与智能体开发",[98,99,100,101,102,103,104,105,106,107,73],"plannotator setup goal","setup","verification","plan","plannotator review","brief","acceptance","create","packages","codex",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":28},"01M6BV26Y6GTDMQZYXFRWKEC08","plannotator-annotate","Open Plannotator's annotation UI for a markdown file, converted HTML file, URL, or folder and then respond to the returned annotations.","https:\u002F\u002Fgithub.com\u002Fdrn\u002Fdots\u002Fblob\u002Fmaster\u002Fagents\u002Fskills\u002Fplannotator-annotate\u002FSKILL.md",[],[115,116,117,118,119],"plannotator annotate","markdown","open","ui","file",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":127,"publishedAt":28},"01M6BV44RGGTRRFGWMYCR3BQ1P","write-skill","Create or improve a Claude Code skill\u002Fslash command with best practices for structure, dynamic context, and safety. Use for creating new skills, improving existing ones, or learning skill authoring.","https:\u002F\u002Fgithub.com\u002Fdrn\u002Fdots\u002Fblob\u002Fmaster\u002Fagents\u002Fskills\u002Fwrite-skill\u002FSKILL.md",[126],{"categoryNo":95,"categoryName":96,"taxonomyType":66,"taxonomyTypeDesc":67},[80,128,129,130,131,132,133,134,135,23,136,137,138,139,140,141,142,143,144,105],"write skill","with","authoring","code skill","code","for","structure","claude code skill","context","command","improve","learning","Safety","best practices","Existing","new","skill authoring",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":28},"01M6BV4390BFK30F1T51SAJPAV","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\".","https:\u002F\u002Fgithub.com\u002Fdrn\u002Fdots\u002Fblob\u002Fmaster\u002Fagents\u002Fskills\u002Fwrapup\u002FSKILL.md",[],[147,152,153,154,133,155,156,157,158,159,23,160,161,162],"session closeout","up","changes","end of day","end","branches","learnings","checklist","session","closeout","capture",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":28},"01M6BV41ZZ051JX2B3CB5WARZM","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.","https:\u002F\u002Fgithub.com\u002Fdrn\u002Fdots\u002Fblob\u002Fmaster\u002Fagents\u002Fskills\u002Ftts\u002FSKILL.md",[],[165,23,22,81,170,171,172,173,27,174,175,176],"speak","text","speech","say","text-to-speech","me","summary"]