Automated summary
This skill enforces a four-part teaching format — analogy, ASCII diagram, step-by-step walkthrough and a common gotcha — whenever the assistant explains code.
Strengths
- A fixed, repeatable structure that prevents scattered explanations
- The ASCII diagram makes flows and relationships between components visible
- Everyday analogies make abstract concepts approachable for non-experts
- The gotcha section surfaces common mistakes instead of leaving them implicit
Limitations
- No length guidance, so explanations can become very verbose on large files
- ASCII diagrams degrade outside monospace interfaces
- Covers explanation only; it does not verify or run the code being described
Reach for it when onboarding someone to an unfamiliar codebase, presenting a module to newcomers, or making a technical concept accessible to a non-expert audience.
Skip it for a quick 'what does this line do' answer, or when the user actually needs a code fix rather than a walkthrough.
Security analysis
SafeThis skill only provides instructions for how to explain code using analogies, ASCII diagrams, and step-by-step walkthroughs. It declares no tools and contains no commands, file operations, network access, or data exfiltration instructions. There is no execution risk.
No concerns found
How this analysis is madeExamples
How does the auth module in src/auth/ work? I just joined the team and I need to understand it.Explain how this debounce implementation works, I don't get why it uses a timer ref.Walk me through how the request flows from the API layer to the database in this repo.name: explain_code description: Explains code with visual diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when the user asks "how does this code work?"
When explaining code, always include:
- Start with an analogy: Compare the code to something from everyday life
- Draw a diagram: Use ASCII art to show the flow, structure, or relationships
- Walk through the code: Explain step-by-step what happens
- Highlight a gotcha: What's a common mistake or misconception?
Keep explanations conversational. For complex concepts, use multiple analogies.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/explain-code-with-analogies-and-diagrams-mrwakedl/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/explain-code-with-analogies-and-diagrams-mrwakedl' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/explain-code-with-analogies-and-diagrams-mrwakedl/download' --output '.skill-downloads/explain-code-with-analogies-and-diagrams-mrwakedl/SKILL.md.part' && mv '.skill-downloads/explain-code-with-analogies-and-diagrams-mrwakedl/SKILL.md.part' '.skill-downloads/explain-code-with-analogies-and-diagrams-mrwakedl/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/explain-code-with-analogies-and-diagrams-mrwakedl/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Supabase Docs Authoring
Documentation
Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.
Create Architecture Decision Record
Documentation
Create a new Architecture Decision Record with sequential numbering, register it in the AgentDB graph, and link related ADRs.
Plan update with deep research
Documentation
Updates a plan document by launching parallel subagents to analyze a topic across all compiler passes, then consolidates findings into the plan doc.