Skip to content
Skills Library
Personal productivity · Learning & explanation

explain

/explain

Explain something in depth on request. Use when the user writes "???" - alone, or placed directly after a reference, statement, or term - which means "explain that in more detail, with a concrete example AND consequences". Also invoked by the /credo:explain command. Treat the pointed-at subject as the thing to explain, never as a literal question, and always answer in the fixed four-part structure: What, Why, Example, Consequences.

Licence
MIT
Last repository change
27.10.2026

Assessment and security

100/ 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.
Content35 / 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
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.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 something in depth on request. Use when the user writes "???" - alone, or placed directly after a reference, statement, or term - which means "explain that in more detail, with a concrete example AND consequences". Also invoked by the /credo:explain command. Treat the pointed-at subject as the thing to explain, never as a literal question, and always answer in the fixed four-part structure: What, Why, Example, Consequences.

Triggers from the description

???
Original author description

Explain something in depth on request. Use when the user writes "???" - alone, or placed directly after a reference, statement, or term - which means "explain that in more detail, with a concrete example AND consequences". Also invoked by the /credo:explain command. Treat the pointed-at subject as the thing to explain, never as a literal question, and always answer in the fixed four-part structure: What, Why, Example, Consequences.

How it works

  1. When to use
  2. Core principle: it is not a literal question
  3. Output structure (fixed - always all four parts)
  4. Guardrails
Original SKILL.md headings · 46 lines, 394 words
SKILL.md preview
---
name: explain
description: Explain something in depth on request. Use when the user writes "???" - alone, or placed directly after a reference, statement, or term - which means "explain that in more detail, with a concrete example AND consequences". Also invoked by the /credo:explain command. Treat the pointed-at subject as the thing to explain, never as a literal question, and always answer in the fixed four-part structure: What, Why, Example, Consequences.
---

# Explain in Depth

Give a thorough, structured explanation of a subject the user wants to understand better. The
subject is whatever the user pointed at: a reference, a statement, or a term. This skill exists
because a short "?" or a raw pointer is not a literal question - it is a request to unpack the
thing properly.

## When to use

- The user writes `???` on its own - they did not understand the last thing and want it explained
  properly.
- The user writes `???` directly after a reference, a statement, or a term (for example
  `the audit gate ???`) - explain that specific thing, not the surrounding sentence.
- The `/credo:explain [subject]` command is run - explain the given subject, or, if none is given,
  the thing the user was just pointing at.

## Core principle: it is not a literal question

`???` and `/credo:explain` are a request to EXPLAIN the referenced thing, not a question to answer
verbatim. Do not reply "yes/no" or treat the `?` marks as asking whether something is true.
Identify the subject, then explain it. If the subject is genuinely ambiguous (nothing recent to
point at, no argument given), ask one short clarifying question first, then explain.

## Output structure (fixed - always all four parts)

Answer in exactly these four labeled parts, in this order, every time:

- **What** - what the subject means. State plainly what is being referred to.
- **Why** - why it is that way, or why it matters. The reasoning or purpose behind it.
- **Example** - one concrete, specific example that makes it tangible.
- **Consequences** - what follows from it: effects, trade-offs, and what happens if it is
  ignored or done differently.

Keep each part focused. Prefer a concrete example over an abstract restatement. Do not add,
rename, drop, or reorder the parts - all four are mandatory, even for a small subject (give a
short answer under each rather than omitting one).

## Guardrails

- Match the language of the surrounding conversation for the explanation itself; the four labels
  stay as What / Why / Example / Consequences.
- Explain the subject only - do not turn the explanation into unrelated advice or actions.
- Honesty applies: if part of the subject is genuinely unknown, say so under the relevant part
  rather than inventing detail.

Versions

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

Database snapshot: 13.11.2026 · package version dcce130b0ee1 (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

  • 100pc-expatiate
    Explain a point, question, or decision in depth so the user can decide. Covers what it means, the implications, the options with pros and cons, and a recommendation. Use when the user asks to expand, explain, or clarify something you raised (an open question, a risk, a blocked…
  • 90understand-explain
    Use when you need a deep-dive explanation of a specific file, function, or module in the codebase
  • 100explain-simply
    Explain something new fast for a smart adult who has never used the topic. Use for "/explain-simply [topic]", "explain this simply", "eli5 this", "break this down for me", "I know nothing about X, catch me up", or another request for a quick plain-language explanation of how something works.

Feedback and reports

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