explain-complex-code

A guided way to explain complicated code in simple language when the user asks for an explanation. It uses a fixed structure such as a short summary, everyday analogy, organisation, execution flow, and possible problems.

In plain words
What is it for?
Use it when someone asks what a file, function, or code section does, how it works, or for an explanation suitable for a beginner. It can cover the code's structure, key mechanisms, sequence of actions, and edge cases.
Why use it?
It helps people understand unfamiliar code without needing to know its technical terms first. Important terms are explained immediately, and longer code gets a more detailed walkthrough.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/kissrosecicd-hub/agents-evolution/explain-complex-code
Any agent
npx skills add kissrosecicd-hub/agents-evolution --skill explain-complex-code
Clone the repo
git clone --depth 1 https://github.com/kissrosecicd-hub/agents-evolution

Made for: Claude Code, Codex.

Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 817 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00041 $0.00817
Opus 5 $0.00020 $0.00409
Sonnet 5 $0.00008 $0.00163
Haiku 4.5 $0.00004 $0.00082

Measured 2d ago against content hash 485cf358a351, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

explain-complex-code scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/explain-complex-code/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Explain Complex Code

Навык объяснять сложный код простым языком. Активируется только по запросу пользователя.

Триггеры

Пользователь говорит:

  • «объясни [код/функцию/файл/это]»
  • «что тут происходит»
  • «разбери» / «разложи»
  • «explain» / «walk me through»
  • «как это работает»
  • «не понимаю этот кусок»
  • «объясни как новичку»
  • «eli5» / «explain like I'm 5»

Формат ответа

Всегда соблюдай структуру:

TL;DR (1-2 строки) → суть без деталей
Аналогия из реального мира → привязка к знакомому
Структура/архитектура → как организовано
Ключевые механизмы → что важно
Поток выполнения → что за чем происходит
Подводные камни → баги, риски, edge cases

Если код короткий — сократи до TL;DR + аналогия + 1 абзац. Если код длинный — добавь все секции.

Правила

Обязательные

  1. TL;DR всегда первым. 1-2 строки. Без TL;DR — ответ провален.
  2. Аналогия из реального мира. Не абстрактная. Физический объект, бытовая ситуация, профессия.
  3. Термин = мгновенное пояснение. Нельзя написать «использует debounce» без «(задержка чтобы не дёргать на каждый чих)».
  4. Код — в code block. Объяснение — вокруг кода, не внутри.
  5. Архитектура — диаграмма текстом. Стрелки, отступы, ASCII. Не «ну ты понял».

Запрещённые

  1. ❌ «Ну это просто...» — для просящего это НЕ просто
  2. ❌ «Очевидно что...» — ничего не очевидно
  3. ❌ «Как вы знаете...» — не предполагаешь уровень
  4. ❌ Ссылка на документацию вместо объяснения
  5. ❌ Пересказ кода строчка-за-строчкой без контекста ЗАЧЕМ

Уровни детализации

Используй gradual.md когда:

  • Пользователь просит «объясни постепенно» / «от простого»
  • Код очень сложный (500+ строк, много абстракций)
  • Пользователь явно новичок

Используй eli5.md когда:

  • Пользователь говорит «объясни как ребёнку» / «eli5» / «на пальцах»
  • Нужно убрать весь жаргон
  • Объясняешь концепцию, не детали реализации

Используй feynman.md когда:

  • Пользователь просит «разбери по шагам» / «как это работает внутри»
  • Нужно понять механизм, не просто «что делает»
  • Готовишься к собеседованию или code review

Read the full file on GitHub · 84 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 84 lines · 41 tokens per session scan A 485cf358a351

Subscribe to this mod's changes

explain-complex-code is a skill published in the GitHub repository kissrosecicd-hub/agents-evolution (31 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 817 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

trulens-notebook-execution

Execute and display Jupyter notebooks for TruLens demos and quickstarts.

truera/trulens · 21 tokens

eli5

Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.

companion-inc/feynman · 63 tokens

deck-course-module

暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.

nexu-io/html-anything · 25 tokens

master-yinguang

Use when user asks about 印光大师, 净土, 念佛, 持名念佛, 十念法, 摄耳谛听, 老实念佛, 信愿行, 带业往生, 仗佛慈力, 自力他力, 竖出横超, 往生, 极乐, 阿弥陀佛, 净土三经, 敦伦尽分, 闲邪存诚, 因果报应, 文钞, 一函遍复, or wants teaching in 印光大师 Yinguang's voice. Triggers include "印光"、"文钞"、"老实念佛"、"信愿行"、"带业往生"、"仗佛慈力"、"横超竖出"、"都摄六根"、"净念相继"、"敦伦尽分"、"闲邪存诚"、"因果"、"十念法"、"摄耳谛听"、"一函遍复"、"净土三经"、"往生" — invoke…

xr843/Master-skill · 274 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

obsidian-to-clew-import

Convert an Obsidian vault or wiki-linked markdown graph into a validated structured-learning graph package for Clew. Use when the user wants to inspect a vault, preview whether it imports cleanly, preserve explicit relation markers, choose only the few import settings that matter, and produce a fail-closed package…

miuuyy/Clew · 72 tokens