Skip to main content

explain (agentic-dev-kit): Clear explanations in

Explain code, flows, bugs, or concepts using the lightest suitable format, starting with clear technical text.

Source facts

Repository
ARYANK-08/agentic-dev-kit
Last source activity
October 2, 2026 at 02:08
Detected SKILL.md language
English
Stars
44
Forks
3

Examples

The source's API-client example replaces a jargon-heavy sentence with three concrete behaviors: attaching a login token, signing out after a 401, and merging identical GET requests. It is an authored wording example, not a tested API implementation.

Uses

For “like I'm 13” or similar requests, the simple mode keeps one everyday analogy, introduces any necessary jargon in plain words, and builds toward a small example. Code explanations are grounded in the actual repository with file and line references.

Prerequisites

The README targets Claude Code and asks for a restart after installation. Rich diagram, HTML, and video routes refer to the Artifact tool and separate artifact-diagramming, artifact-design, and faceless-explainer skills.

How to use

Ask to explain code, a flow, a bug, a concept, or an architecture; the source says this matches the skill automatically. The response starts with a one-line answer, explains the mechanism, and gives a concrete input/output example. Say “like I'm 13” to request the analogy-based mode.

Limitations

The writing rules use a relaxed ASD-STE100 approach, not a claim of formal compliance. Small questions stay in text; a video is generated only when requested. Rich-format routes depend on the separate tools and skills named in the instructions.

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
nameexplain
descriptionUse whenever the user asks to explain, walk through, or help them understand anything (code, a flow, a bug, a concept, an architecture, a model output). Picks the clearest output format and writes in simplified technical English.