Use when user invokes /explain with a file path, directory path, function/class name, or natural language concept. Also triggers on "explain this", "how does X work", "walk me through". Produces a structured, layered explanation of what the code does, how it connects, and where to start if you need to change it. Do NOT use when the user wants to trace data flow through a pipeline — use /lineage in
The exact command may vary by repository. Check the README on GitHub.
For the skill author
Drop this on your repo README
Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.
[](https://www.skillteca.com.br/skills/explain-harnessprotocol?utm_source=badge&utm_medium=readme&utm_campaign=badge)
One short email with only the new Dados e Análise skills. 4 minutes of reading, no spam, unsubscribe with one click.
You confirm your email on the first send. No spam. Unsubscribe with one click.
Structured Code Explainer
Overview
Produce layered explanations of code — files, directories, functions, classes, or cross-cutting concepts. Designed for developers working in unfamiliar parts of a codebase.
Core principles:
Adaptive depth. A single function gets a focused deep-dive. A directory gets a map first, then the user picks where to zoom.
Project-aware. If the project has a CLAUDE.md, reference its Architecture section to ground explanations in the project's ow
[Description truncada. Veja o README completo no GitHub.]
