Skip to content
Back to skills

Explain

ASecurity

Explain code in plain language

  • 147 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 3, 2026
ai-agentsgoapidocumentation

Works with

  • api

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add prapaa-ai/agav --skill explain --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Explain?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Explain
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/prapaa-ai-explain/badge)](https://www.skillsdirectory.com/skills/prapaa-ai-explain)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: explain
description: Explain code in plain language
version: 1.0.0
invocation: both
allowed-tools: read_file grep_search find_files list_directory
tags:
  - understanding
  - documentation
---

# Explain

Explain code in clear, plain language so the user understands what it does and why.

## Instructions

1. Read the specified file or code region in full.
2. Identify the purpose of the code: what problem it solves and where it fits in the broader system.
3. Explain the high-level logic first, then drill into important details:
   - **What it does**: Summarize the behavior in one or two sentences.
   - **How it works**: Walk through the control flow, key algorithms, and data transformations step by step.
   - **Why it's structured this way**: Explain design decisions, patterns used (e.g., factory, observer, middleware), and trade-offs.
4. Describe the data flow: what comes in, how it's transformed, and what goes out.
5. Highlight integration points: what other modules, APIs, or services this code depends on or exposes.
6. Call out non-obvious behavior: implicit assumptions, gotchas, or side effects a reader might miss.
7. Adjust the explanation depth to the user's level. Default to an intermediate developer audience unless told otherwise.
8. Use concrete examples where they clarify abstract logic.
9. Keep the explanation structured with short paragraphs or bullet points for readability.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…