⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

version unknown

explain

@aantoniadis⭐ 0 stars

Explains how existing code behaves for one question or feature, tracing a concrete flow to pinned source lines, with a reusable note or HTML page when selected. Use when the user asks how something works, wants a flow traced, needs onboarding to an area of a codebase, or wants to understand code before changing it. Not for deciding what to change (plan-change) or finding defects in a diff (find-bugs).

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

Adopt or update this skill from https://proskills.md/skills/other/aantoniadis-skills-skills-explain. First identify the installation path supported by this platform, detect whether it is already installed, compare the installed version with the latest stable release, show me what will change, and only then install or update it. If no native installer is available, use the complete package or source fallback described on the page.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

Download the complete ZIP

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars

⭐ 0 on GitHubGitHub ↗

New / niche

🟢ProSkills Score

—

📍

Not yet listed on ClawHub or SkillsMP

// README

skills

Skills for coding agents, shipped as the aantoniadis-skills plugin for Claude Code, Codex, and OpenCode. Six skills cover the work around a change: set a project up for evidence, understand the code, plan the behavior, fix a reported bug, find the defects, and review the PR. Matt Pocock's and HumanLayer's originals, installed separately, carry a plan through spec, tickets, implementation, and the PR.

claude plugin marketplace add aantoniadis/skills && claude plugin install aantoniadis-skills@aantoniadis

Invoke a skill as /aantoniadis-skills:<name> in Claude Code, $aantoniadis-skills:<name> in Codex, and through the /skills menu or opencode run --command <name> in OpenCode. Hosts also pick the skills up through their normal model-driven selection.

Install

# Claude Code
claude plugin marketplace add aantoniadis/skills
claude plugin install aantoniadis-skills@aantoniadis

# Codex
codex plugin marketplace add aantoniadis/skills
codex plugin add aantoniadis-skills@aantoniadis

The skills run Python 3 scripts. The page checker and renderer need two packages; HTML pages with diagrams also use Node.js (renderer options):

python3 -m pip install markdown-it-py beautifulsoup4

OpenCode loads the plugin from opencode.json, from Git or from a checkout:

{ "plugin": ["@aantoniadis/skills@git+https://github.com/aantoniadis/skills.git"] }

{ "plugin": ["/path/to/skills/opencode/skills.js"] }

Start a new session after an install or update.

Updates. Every merge to the default branch is a release. Codex reinstalls the plugin when it starts on new commits. Claude Code updates by hand, or on its own once auto-update is on for the aantoniadis marketplace under /plugin:

claude plugin marketplace update aantoniadis && claude plugin update aantoniadis-skills@aantoniadis

OpenCode caches a Git-installed plugin; delete ~/.cache/opencode/packages/@aantoniadis to fetch the current version. A checkout updates with git pull. For development, claude --plugin-dir <checkout> runs the checkout directly.

Original skills

Our skills work with six originals: Matt Pocock's grilling, to-spec, to-tickets, and implement, and HumanLayer's show-me and visual-pr. Install them once per machine, one route per host:

# Matt Pocock's skills: Claude Code
claude plugin install mattpocock-skills@claude-plugins-official
# Matt Pocock's skills: Codex
codex plugin marketplace add mattpocock/skills
codex plugin add mattpocock-skills@mattpocock
# Matt Pocock's skills: OpenCode and other hosts (-a <agent> selects the host)
npx skills@latest add mattpocock/skills -g
# HumanLayer's skills: every host
npx skills@latest add humanlayer/skills --skill show-me --skill visual-pr -g

setup-tools records where each copy is. Our skills name them mattpocock:implement or humanlayer:visual-pr (skills/REFERENCES.md) and respect each author's choice of who runs it: plan-change invokes grilling through the host; the other five are user-invoked, so our skills finish their own deliverable and hand you the command, such as /mattpocock-skills:to-spec in Claude Code or /to-spec after an npx skills install. Each original then runs its own workflow, unchanged.

The skills

Skill	Use it when	You get	How it works
`setup-tools`	Reusable preparation or repair would help the intended work	Useful tools checked, with a local untracked record when there is preparation to retain	docs/setup-tools.md
`explain`	You need to know how a flow works before touching it	A source-cited answer, with a reusable note or HTML page when selected	docs/explain.md
`plan-change`	A ticket is vague and the change has consequences beyond its own function	A plan with named decisions, preserved behavior, evidence, and acceptance scenarios	docs/plan-change.md
`find-bugs`	You want the defects in a change before it merges, or before you review it	Ranked defects with evidence, material questions, and review limits	docs/find-bugs.md
`fix-bug`	A test fails, an issue reports wrong behavior, or production shows a symptom	A demonstrated cause, a fix with a regression test that went red then green, and a diagnosis page a reviewer can verify	docs/fix-bug.md
`pr-review-guide`	You have to review a PR you did not write	A guide to a pinned snapshot: what the change means, where to look, what to skim, what to ask the author	docs/pr-review-guide.md

The skills start from context and settled choices, and ask only about open preferences or consequential decisions. Every claim sits next to its evidence: a pinned line, an executed check, a quote, or a label such as inferred or not inspected. setup-tools keeps what it learns in a local record outside the repository.

With the originals: plan-change hands agreed decisions to Matt's to-spec and to-tickets, Matt's implement builds an unblocked ticket, fix-bug takes a reported symptom to a fixed, recorded cause, find-bugs runs before HumanLayer's visual-pr opens the PR, and pr-review-guide serves the PR's human reviewer. An original invoked directly keeps its own behavior, such as committing or pushing; one called by our skills follows our task constraints.

Using the skills together: copyable prompts, project setup, handoffs, and artifact locations
The light path: a shorter workflow for contained changes in familiar code

License

MIT. Bundled third-party assets, the Manrope font and highlight.js, keep their own licenses; THIRD-PARTY-NOTICES.md lists them.

// HOW IT'S BUILT

KEY FILES

skills/explain/SKILL.mdREADME.md

// REPO STATS

0 stars

// SHARE

Share on X Share on LinkedIn