How do I install the Ase Code Explain skill?

Run npx skillmds add majiayu000/ase-code-explain in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ase Code Explain safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ase Code Explain?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ase Code Explain free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ase Code Explain?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ase Code Explain by majiayu000 — Agent Skill

Name: Ase Code Explain
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md

First, explain WHAT the code does (functionality). Second, explain WHY the code does it (rationale).

Keep your explanations brief and concise. Output the result with the following :

WHY (You should know why):
- [...]
- [...]
- [...]
First, give an analogy by comparing the code to something from everyday life. How can I understand this by something I already know? Use simple wording as in "Explain Like I'm 5 Years Old (ELI5)" style of explanations. For very complex concepts, use multiple analogies.

Second, draw a diagram to show the control or data flow, code or data structure, or code or data relationships. What gives the best overall overview of the code? Build a Mermaid specification , choosing the Mermaid diagram type per intent: classDiagram for class/method structure, sequenceDiagram for actor/message flow, or flowchart TB for boxes-and-lines component layouts. Then dispatch the rendering to the ase-meta-diagram sub-agent by calling the tool Agent(name: "ase-meta-diagram", description: "Diagram Rendering", subagent_type: "ase:ase-meta-diagram", prompt: <mermaid-spec/>) and reproduce its returned fenced code block verbatim in the response text. Do not hand-draw.

Keep your explanation brief and concise. Output the result with the following :

DIAGRAM (You should grasp): [...]
First, tell what are the cruxes of the code. Is there something one should really notice?

Second, tell what are the gotchas of the code. Is there something one could really stumble over?

Keep your explanation brief and concise. Output the result with the following :

GOTCHAS (You should not stumble over):
- [...]
- [...]
- [...]

---name: ase-code-explaindescription: Explains code with WHAT, WHY, ANALOGY, DIAGRAM, CRUXES, and GOTCHAS. Use when you want to know how code works or when the user asks "how does this work?"--- @${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md <skill name="ase-code-explain"> Explain Source Code </skill> <expand name="getopt" arg1="ase-code-explain"> $ARGUMENTS </expand> <objective> *Analyze* the source code of <getopt-arguments/>, and its directly related source code and *explain* it in a *brief*, *standardized*, and *concise* way. </objective> <flow> 1. <step id="STEP 1: Investigate Code Base"> Investigate the code. If the code base is large, you *MUST* use the `Agent` tool (not inline work) to create multiple sub-agents to split the investigation task into appropriate chunks. </step> 2. <step id="STEP 2: WHAT and WHY"> **Explain the WHAT and WHY**. First, explain *WHAT* the code does (*functionality*). Second, explain *WHY* the code does it (*rationale*). Keep your explanations *brief* and *concise*. Output the result with the following <template/>: <template> <ase-tpl-bullet-normal/> **WHAT** (You should know what): - [...] - [...] - [...] <ase-tpl-bullet-normal/> **WHY** (You should know why): - [...] - [...] - [...] </template> </step> 3. <step id="STEP 3: ANALOGY and DIAGRAM"> **Give insights with ANALOGY and DIAGRAM**. First, give an analogy by comparing the code to something from everyday life. How can I understand this by something I already know? Use simple wording as in "Explain Like I'm 5 Years Old (ELI5)" style of explanations. For very complex concepts, use multiple analogies. Second, draw a diagram to show the control or data flow, code or data structure, or code or data relationships. What gives the best overall overview of the code? Build a Mermaid specification <mermaid-spec/>, choosing the Mermaid diagram type per intent: `classDiagram` for class/method structure, `sequenceDiagram` for actor/message flow, or `flowchart TB` for boxes-and-lines component layouts. Then dispatch the rendering to the `ase-meta-diagram` sub-agent by calling the tool `Agent(name: "ase-meta-diagram", description: "Diagram Rendering", subagent_type: "ase:ase-meta-diagram", prompt: <mermaid-spec/>)` and reproduce its returned fenced code block verbatim in the response text. Do *not* hand-draw. Keep your explanation *brief* and *concise*. Output the result with the following <template/>: <template> <ase-tpl-bullet-secondary/> **ANALOGY** (You should imagine): - [...] - [...] - [...] <ase-tpl-bullet-secondary/> **DIAGRAM** (You should grasp): [...] </template> </step> 4. <step id="STEP 4: CRUXES and GOTCHAS"> **Highlight CRUXES and GOTCHAS**. First, tell what are the *cruxes* of the code. Is there something one should really *notice*? Second, tell what are the gotchas of the code. Is there something one could really *stumble over*? Keep your explanation *brief* and *concise*. Output the result with the following <template/>: <template> <ase-tpl-bullet-signal/> **CRUXES** (You should notice): - [...] - [...] - [...] <ase-tpl-bullet-signal/> **GOTCHAS** (You should not stumble over): - [...] - [...] - [...] </template> </step> </flow>

Frequently asked questions