How do I install the Code Explanation skill?

Run npx skillmds@latest add thalysjuvenal/code-explanation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Code Explanation safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Code Explanation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Code Explanation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Code Explanation?

thalysjuvenal (@thalysjuvenal) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Code Explanation by thalysjuvenal — Agent Skill

Name: Code Explanation
Author: thalysjuvenal

Code Explanation

Use when the user asks to explain what a piece of ADVPL/TLPP code does in plain language, adapting the explanation depth for a junior developer (line-by-line), a senior developer (business logic, design decisions, risks), or a functional consultant (no technical terms) -- e.g. understanding legacy code, filling in missing documentation, or assessing the impact of a customization. Also triggers on Portuguese phrasing like "explicar fonte", "explicar codigo", "o que essa rotina faz", "explicar para o consultor funcional", or requests for a --level junior/senior/funcional explanation.

thalysjuvenal 25aa447 2 files · 4.6 KB Updated Sep 17, 2026

File contents

ADVPL/TLPP Code Explanation

This skill provides a methodology for explaining existing ADVPL/TLPP code in plain language, tailored to three audience levels: a junior developer needing line-by-line detail, a senior developer needing a business-logic summary with risks and technical debt, and a functional consultant needing a non-technical description of what the routine does from a business perspective.

Activate this skill when the user wants an existing routine, function, or snippet explained -- e.g. onboarding a new developer, understanding legacy code with no documentation, or briefing a functional consultant on a customization. It reads the target code, determines the requested (or asked) explanation level, and structures the output accordingly, optionally pulling in native-function meanings, business-process context, or SQL details as needed.

It does not cover generating formal documentation artifacts like Protheus.doc headers or full routine specs (see documentation-patterns), looking up native function syntax in isolation (see protheus-reference), or explaining embedded SQL macro semantics in depth (see embedded-sql).

Reference file	Read when
reference.md	Always -- explanation levels, structure per level (junior/senior/funcional), and the analysis process

Frequently asked questions