Automated summary
This skill turns the explanation of complex code into a structured teaching walkthrough, with a high-level summary, step-by-step exploration, and diagrams or annotated snippets.
Strengths
- Clear output structure: summary, walkthrough, diagrams, pitfalls, and next steps
- Progressive-disclosure approach suited to developers at all levels
- Highlights complexity hotspots, edge cases, and key terminology
- Ships a resources playbook for deeper worked examples
Limitations
- Focused on analysis and teaching, not implementation or refactoring
- Does not produce API docs or end-user documentation
- Requires existing code or design to analyze
Use it when you need to understand or teach a piece of code, algorithm, or architecture, such as during review or onboarding.
Avoid it when the request is to build new features, refactor code, or only write API documentation.
Security analysis
SafeThis is a documentation/explanation skill with no declared tools and no instructions to execute commands, access secrets, modify files, or use network/docker resources. Its risk is limited to ordinary text guidance.
No concerns found
How this analysis is madeExamples
Explain how the rate-limiting middleware in src/middleware/rateLimit.ts works, step by step, with a diagram of the token bucket logic and the edge cases I should watch for.I'm new to this repo. Walk me through the request lifecycle from the HTTP entrypoint to the database layer, highlighting the key components and any pitfalls.Help me understand why this recursive function returns the wrong value — break down the execution flow with pseudocode and point out where the logic diverges.name: code-documentation-code-explain description: "You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable expl..." risk: unknown source: community
Code Explanation and Analysis
You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable explanations for developers at all levels.
Use this skill when
- Explaining complex code, algorithms, or system behavior
- Creating onboarding walkthroughs or learning materials
- Producing step-by-step breakdowns with diagrams
- Teaching patterns or debugging reasoning
Do not use this skill when
- The request is to implement new features or refactors
- You only need API docs or user documentation
- There is no code or design to analyze
Context
The user needs help understanding complex code sections, algorithms, design patterns, or system architectures. Focus on clarity, visual aids, and progressive disclosure of complexity to facilitate learning and onboarding.
Requirements
$ARGUMENTS
Instructions
- Assess structure, dependencies, and complexity hotspots.
- Explain the high-level flow, then drill into key components.
- Use diagrams, pseudocode, or examples when useful.
- Call out pitfalls, edge cases, and key terminology.
- If detailed examples are required, open
resources/implementation-playbook.md.
Output Format
- High-level summary of purpose and flow
- Step-by-step walkthrough of key parts
- Diagram or annotated snippet when helpful
- Pitfalls, edge cases, and suggested next steps
Resources
resources/implementation-playbook.mdfor detailed examples and templates.
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/code-explanation-and-analysis-mrzxur3p/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/code-explanation-and-analysis-mrzxur3p' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/code-explanation-and-analysis-mrzxur3p/download' --output '.skill-downloads/code-explanation-and-analysis-mrzxur3p/SKILL.md.part' && mv '.skill-downloads/code-explanation-and-analysis-mrzxur3p/SKILL.md.part' '.skill-downloads/code-explanation-and-analysis-mrzxur3p/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.
Original excerpt: Requirements
$ARGUMENTS
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
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/code-explanation-and-analysis-mrzxur3p/SKILL.md' && test -s '.skill-downloads/code-explanation-and-analysis-mrzxur3p/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/code-documentation-code-explain' && cp -R '.skill-downloads/code-explanation-and-analysis-mrzxur3p' '.claude/skills/code-documentation-code-explain'Cursor
test -f '.skill-downloads/code-explanation-and-analysis-mrzxur3p/SKILL.md' && test -s '.skill-downloads/code-explanation-and-analysis-mrzxur3p/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/code-documentation-code-explain' && cp -R '.skill-downloads/code-explanation-and-analysis-mrzxur3p' '.cursor/skills/code-documentation-code-explain'Codex
test -f '.skill-downloads/code-explanation-and-analysis-mrzxur3p/SKILL.md' && test -s '.skill-downloads/code-explanation-and-analysis-mrzxur3p/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/code-documentation-code-explain' && cp -R '.skill-downloads/code-explanation-and-analysis-mrzxur3p' '.agents/skills/code-documentation-code-explain'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/code-explanation-and-analysis-mrzxur3p'openskills read 'code-explanation-and-analysis-mrzxur3p'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual 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/code-explanation-and-analysis-mrzxur3p/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.