[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74GD36BGDRXJ5RSCDC80N1C":3,"skill-same:01M74GD36BGDRXJ5RSCDC80N1C":50},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M74GD36BGDRXJ5RSCDC80N1C","explain",null,"Explain a concept at a specified audience tier (ELI5 \u002F curious-undergrad \u002F experienced-peer \u002F domain-expert); pick the analogy and abandon it before it lies.","MohammadBafkar\u002Fpolymath","MohammadBafkar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34940462?v=4","01M74G540TQFZWK6KVAPKFVGNR","Mohammad Bafkar","01M74G541HG19QP9V5DQCJVKYE",0,"MIT","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-learning\u002Fskills\u002Fexplain\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: explain\ndescription: Explain a concept at a specified audience tier (ELI5 \u002F curious-undergrad \u002F experienced-peer \u002F domain-expert); pick the analogy and abandon it before it lies.\n---\n\n# explain\n\n> Explanations fail when the audience tier is implicit. Pick the tier first, then the analogy, then the where-the-analogy-breaks.\n\n**Mode:** generative — diverge before converging. Produce genuinely different options first (the obvious answer is one candidate, not the answer), then narrow with stated criteria.\n\n## When to use\n\n- The user asks \"explain X\" or \"how does Y work?\".\n- A workflow needs to teach a concept before a decision.\n- Onboarding a new contributor on an unfamiliar area.\n\n## Inputs\n\n- The concept (required).\n- Audience tier (one of: `eli5`, `curious-undergrad`, `experienced-peer`, `domain-expert`). If unstated, infer it from how the user writes and name the tier you chose at the top; ask only when the guess would change the answer a lot.\n- Optional: domain context (what the audience already knows).\n\n## Procedure\n\n1. **Pin the tier**. Each tier has a different contract:\n   - **ELI5**: a 5-year-old hears it and gets the *vibe*. Concrete objects, one analogy, no jargon. Accept that detail is lost.\n   - **Curious undergrad**: 1–2 paragraphs. One analogy, one limit of the analogy, one terminology bridge.\n   - **Experienced peer**: skip the analogy. Compare to something they already know in this domain. Cite the mechanism, not the metaphor.\n   - **Domain expert**: zero analogy. Talk about the specific thing — what's load-bearing, what's a footgun, what's commonly misunderstood.\n2. **For ELI5 and undergrad**: draft three candidate analogies from *different* domains (kitchen, traffic, a library, a sport, …) before choosing — the first analogy that comes to mind is usually the most worn. Pick the one whose breaking point matters least for this audience's next question, then immediately state where it breaks. An analogy that doesn't disclose its limits will mislead the learner.\n3. **For peer and expert**: pick a single reference point in their existing knowledge. \"Like X but Y\" beats invented metaphor.\n4. **One concept per pass**. If you need to explain a prerequisite first, stop and explain the prerequisite alone first.\n\n## Output\n\n```text\nexplain: \u003Cconcept> — tier: \u003CELI5 | undergrad | peer | expert>\n\n[content following the tier contract]\n\n[For ELI5 \u002F undergrad only] Where the analogy breaks:\n  - \u003Cone or two specific limits>\n```\n\n## Quality bar\n\n- Tier is named at the top.\n- ELI5 \u002F undergrad → analogy + its limit, chosen from three candidates in different domains (not the stock one by default).\n- Peer \u002F expert → no invented metaphor; reference existing knowledge.\n- One concept per explanation. If a prerequisite is needed, surface it.\n\n## Anti-patterns to avoid\n\n- ELI5 that slips in jargon (\"it's like a hash table\"). Not 5-year-old.\n- Expert explanation that wastes time on prerequisites the expert already knows.\n- Analogy without limits (\"the kernel is like a librarian\"). Misleads.\n- Trying to cover multiple concepts in one explanation; the audience leaves with none.\n","# explain\n\n> Explanations fail when the audience tier is implicit. Pick the tier first, then the analogy, then the where-the-analogy-breaks.\n\n**Mode:** generative — diverge before converging. Produce genuinely different options first (the obvious answer is one candidate, not the answer), then narrow with stated criteria.\n\n## When to use\n\n- The user asks \"explain X\" or \"how does Y work?\".\n- A workflow needs to teach a concept before a decision.\n- Onboarding a new contributor on an unfamiliar area.\n\n## Inputs\n\n- The concept (required).\n- Audience tier (one of: `eli5`, `curious-undergrad`, `experienced-peer`, `domain-expert`). If unstated, infer it from how the user writes and name the tier you chose at the top; ask only when the guess would change the answer a lot.\n- Optional: domain context (what the audience already knows).\n\n## Procedure\n\n1. **Pin the tier**. Each tier has a different contract:\n   - **ELI5**: a 5-year-old hears it and gets the *vibe*. Concrete objects, one analogy, no jargon. Accept that detail is lost.\n   - **Curious undergrad**: 1–2 paragraphs. One analogy, one limit of the analogy, one terminology bridge.\n   - **Experienced peer**: skip the analogy. Compare to something they already know in this domain. Cite the mechanism, not the metaphor.\n   - **Domain expert**: zero analogy. Talk about the specific thing — what's load-bearing, what's a footgun, what's commonly misunderstood.\n2. **For ELI5 and undergrad**: draft three candidate analogies from *different* domains (kitchen, traffic, a library, a sport, …) before choosing — the first analogy that comes to mind is usually the most worn. Pick the one whose breaking point matters least for this audience's next question, then immediately state where it breaks. An analogy that doesn't disclose its limits will mislead the learner.\n3. **For peer and expert**: pick a single reference point in their existing knowledge. \"Like X but Y\" beats invented metaphor.\n4. **One concept per pass**. If you need to explain a prerequisite first, stop and explain the prerequisite alone first.\n\n## Output\n\n```text\nexplain: \u003Cconcept> — tier: \u003CELI5 | undergrad | peer | expert>\n\n[content following the tier contract]\n\n[For ELI5 \u002F undergrad only] Where the analogy breaks:\n  - \u003Cone or two specific limits>\n```\n\n## Quality bar\n\n- Tier is named at the top.\n- ELI5 \u002F undergrad → analogy + its limit, chosen from three candidates in different domains (not the stock one by default).\n- Peer \u002F expert → no invented metaphor; reference existing knowledge.\n- One concept per explanation. If a prerequisite is needed, surface it.\n\n## Anti-patterns to avoid\n\n- ELI5 that slips in jargon (\"it's like a hash table\"). Not 5-year-old.\n- Expert explanation that wastes time on prerequisites the expert already knows.\n- Analogy without limits (\"the kernel is like a librarian\"). Misleads.\n- Trying to cover multiple concepts in one explanation; the audience leaves with none.\n",{"name":5,"description":7},"main","23f6e21841a39580c9da2b5ec941f39dda17cd86","plugins\u002Fpolymath-learning\u002Fskills\u002Fexplain","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath","https:\u002F\u002Fgithub.com\u002FMohammadBafkar","2026-10-29 18:34:59",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add MohammadBafkar\u002Fpolymath --skill explain",{"tool":36,"command":37},"bunx","bunx skills add MohammadBafkar\u002Fpolymath --skill explain",{"tool":39,"command":40},"pnpm","pnpm dlx skills add MohammadBafkar\u002Fpolymath --skill explain","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-learning\u002Fskills\u002Fexplain\u002FSKILL.md",true,[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"routing.yaml","REFERENCE","参考文档",319,"https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-learning\u002Fskills\u002Fexplain\u002Frouting.yaml",[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M74GN87EBRHM9N87M7AP1HDD","runbook","Write or refresh an operational runbook for an alert\u002Fsymptom; structured as TL;DR + Pre-checks + Steps + Verification + Rollback + Escalation.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Frunbook\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M74GN5GPKEC1JEKP2DFQNEQJ","rfc","Draft a lightweight design RFC to docs\u002Frfcs\u002F\u003Cslug>.md; Summary, Motivation, Detailed design, Drawbacks, Alternatives, Unresolved questions. A proposal to debate, not a recorded decision (adr).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Frfc\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M74GN2F4CWPMV4X09TG4E304","editorial-pass","Review and tighten prose in a Markdown artifact for a target tone (terse, formal, friendly) without dropping information; preserve quotations and load-bearing constraints.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Feditorial-pass\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M74GMZWGYMZ37C4DYGT6P23G","architecture-review-facilitation","Run an architecture review as a process — entry criteria, reviewer checklist, decision log, and follow-up actions — pairing the design artifact with a red-team pass.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Farchitecture-review-facilitation\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M74GMXVX0YX3ETDXS527XDGM","architecture-doc","Write a C4-style architecture document; System Context + Containers (+ Components when interesting) with mermaid diagrams. Describes structure, not a decision (adr) or proposal (rfc).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Farchitecture-doc\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M74GMVG1WSMCK066S3KE6V5K","adr","Write an Architecture Decision Record (Michael Nygard format) to docs\u002Fadrs\u002FNNNN-\u003Cslug>.md; frontmatter validated by the ADR artifact schema. Records a made decision, not a proposal to debate (rfc).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Fadr\u002FSKILL.md",[],[]]