Skip to content
Skills Library
Programming · Learning & explanation

explain

/explain

Explain a technical concept (commit, repository, branch, environment variable, port, database, API, front end/back end, deploy, DNS, domain, build, test, lint, dependency, or any other) in plain language, applied to the user's own Builder project. Use when the user asks what a term means, or runs /builder:explain <concept>.

Licence
MIT
Last repository change
11.11.2026

Assessment and security

96/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content31 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
16
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Explain a technical concept (commit, repository, branch, environment variable, port, database, API, front end/back end, deploy, DNS, domain, build, test, lint, dependency, or any other) in plain language, applied to the user's own Builder project. Use when the user asks what a term means, or runs /builder:explain <concept>.

Arguments

/explain <concept>
Original author description

Explain a technical concept (commit, repository, branch, environment variable, port, database, API, front end/back end, deploy, DNS, domain, build, test, lint, dependency, or any other) in plain language, applied to the user's own Builder project. Use when the user asks what a term means, or runs /builder:explain <concept>.

How it works

SKILL.md has no level-two headings · 16 lines, 174 words

SKILL.md preview
---
name: explain
description: Explain a technical concept (commit, repository, branch, environment variable, port, database, API, front end/back end, deploy, DNS, domain, build, test, lint, dependency, or any other) in plain language, applied to the user's own Builder project. Use when the user asks what a term means, or runs /builder:explain <concept>.
argument-hint: <concept>
---

# Explain a concept

The user wants to understand a term: `$ARGUMENTS` (or the one they asked about).

Read `${CLAUDE_PLUGIN_ROOT}/skills/_shared/tone.md`, and `builder/state.json` if it exists (for the language, the experience level and the project).

1. If there's a note for it in `${CLAUDE_PLUGIN_ROOT}/skills/explain/concepts/` (file names: `commit`, `repository`, `branch`, `environment-variable`, `port`, `database`, `api`, `frontend-backend`, `deploy`, `dns`, `domain`, `build`, `test`, `lint`, `dependency`), use it as the base. Otherwise, explain from your own knowledge with the same shape.
2. Answer in at most ~120 words, in `profile.language`:
   - **What it is**: one or two plain sentences, with an everyday comparison if it helps.
   - **Why it matters here**: tied to *this* project and its current phase.
   - **Example**: one line from the user's own project (their files, their tasks, their app). If there is no project yet, use a simple example.
3. Adjust the depth to `profile.codingExperience`: simplest for `none`, a bit more precise for `some`, short and technical for `developer`.

Don't change any file. End by offering to go back to what they were doing (`/builder:next`).
Files in this package (16)
  • SKILL.md 2 KB
  • concepts/api.md 1 KB
  • concepts/branch.md 1 KB
  • concepts/build.md 1 KB
  • concepts/commit.md 1 KB
  • concepts/database.md 1 KB
  • concepts/dependency.md 1 KB
  • concepts/deploy.md 1 KB
  • concepts/dns.md 1 KB
  • concepts/domain.md 1 KB
  • concepts/environment-variable.md 1 KB
  • concepts/frontend-backend.md 1 KB
  • concepts/lint.md 1 KB
  • concepts/port.md 1 KB
  • concepts/repository.md 1 KB
  • concepts/test.md 1 KB

Versions

RepositoryScoreLicence
This page · librosdeia/builder-method-claude-plugin96MIT
crbnos/carbon100AGPL-3.0
PerilloAI/flowtrace-plugin100Apache-2.0
mickeyyaya/evolve-loop100Apache-2.0
zenobi-us/dotfiles100MIT
imgly/agent-skills100MIT
marcel-bich/marcel-bich-claude-marketplace100MIT
nicodiansk/draw-it-out100MIT
ramboz/jig100MIT

Database snapshot: 13.11.2026 · package version 93d7fc5e482f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90st-explain
    Explain how a piece of code works, why it is built that way, and what that means, in plain language a person can follow. Use for 'how does X work', 'why is it like this', 'teach me this', onboarding to a subsystem, or /st-explain.
  • 90ds-explain
    Explain how a piece of code works, why it is built that way, and what that means, in plain language a person can follow. Use for 'how does X work', 'why is it like this', 'teach me this', onboarding to a subsystem, or /ds-explain.
  • 100audit-verify-explain-grade-5
    Audit work, verify claims with concrete evidence, and explain the result in simple grade-5 language. Use when the user asks to review, audit, check, verify, explain a change, explain a fix, summarize test results, validate whether something works, or translate technical findings…
  • 95how
    Explain how the current project, a feature, or a code path works in plain language for a beginner. Use when the user wants to understand an existing codebase or how its parts work together.
  • 90eli5
    Explain an engineering concept, standard, calculation, or design in plain language with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "explain like I'm 5", "ELI5 this", asks for a simple explanation of a technical/engineering topic, wants jargon…
  • 90diff-explain
    Use when you want a one-paragraph plain-English summary of what a diff does. Activates on "summarize this diff", "what does this PR do", "explain this branch", or when pointed at a PR URL or local branch.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.