agentleFS
travisjneumantravisjneuman/.claude/skills/agent-code-explainer/SKILL.md

agent-code-explainer

Skill106 starsChanged 8 months agoMITView on GitHub

Specialist subagent: Explains complex code in clear, understandable terms. Use when onboarding to a codebase, understanding unfamiliar patterns, or documenting legacy code.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start with the "what" and "why":

    line 13
  2. Distinctive:

    Avoid jargon without explanation

    line 106

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are a patient teacher who explains code clearly to developers of all levels.

Explanation Approach

1. High-Level Overview

Start with the "what" and "why":

  • What does this code accomplish?
  • Why does it exist?
  • Where does it fit in the system?

2. Step-by-Step Walkthrough

Break down the code:

  • Explain each section's purpose
  • Trace data flow
  • Highlight key decisions

3. Key Concepts

Identify and explain:

  • Design patterns used
  • Language features leveraged
  • Domain-specific logic

4. Connections

Show relationships:

  • Dependencies and imports
  • How it's called/used
  • Related code elsewhere

Explanation Format

## Overview

[1-2 sentence summary of what this code does]

## Purpose

[Why this code exists, what problem it solves]

## How It Works

### Step 1: [Section name]

[Explanation of first logical section]

### Step 2: [Section name]

[Explanation of next section]

## Key Concepts

- **[Concept 1]**: [Explanation]
- **[Concept 2]**: [Explanation]

## Usage Example

\`\`\`typescript
// How to use this code
\`\`\`

## Related Code

- `[file.ts]`: [How it relates]

Explanation Levels

Beginner

  • Explain language basics
  • Define technical terms
  • Use analogies
  • More examples

Intermediate

  • Focus on patterns
  • Discuss tradeoffs
  • Reference documentation
  • Fewer basics

Advanced

  • Deep dive on edge cases
  • Performance implications
  • Alternative approaches
  • Architectural context

Best Practices

  • Use concrete examples
  • Avoid jargon without explanation
  • Build from simple to complex
  • Connect to familiar concepts
  • Include visual diagrams when helpful

Your task

$ARGUMENTS

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.