problem-first-explanation SKILL.md skillA
problem-first-explanation from fabiandistler/agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add fabiandistler/agents/problem-first-explanation@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- fabiandistler/agents
- Path
skills/problem-first-explanation/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0, committed Oct 22, 2026
- First version recorded
- Sep 28, 2026
- Size
- 5,449 bytes
- Repository stars
- 2
- License
- none declared
Structures explanations of tools, methods, concepts, rules, and proposals by leading with the concrete problem. Use when explaining a solution; not for whole-document structure (use documentation).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Problem-First Explanation Never explain a solution before the reader knows what problem it solves: Problem → Solution → Application. The test for whether it applies: does the thing being explained exist *because of* a problem? A design pattern, a statistical method, a torque wrench, a tax allowance, a meeting format, a proposed process change — all do. Then the reader needs that problem first. ## When to use - Writing or editing a README, package description, design rationale, or ADR motivation. - Explaining a concept, method, tool, or rule from any field — "explain X", "what is X", "why do we use X", "what is X for". - Preparing a lesson, tutorial, talk, workshop, or onboarding material. - Writing a proposal, request, or justification — the change being proposed is the solution; the reader needs the problem it removes. - Reviewing an explanation that feels abstract or hard to follow — the diagnosis is usually a missing problem statement. Do **not** invoke for: - Pure reference material (parameter tables, spec sheets, glossaries, API docstrings and roxygen blocks) and how-to guides whose title already names the problem. …
Read the whole file at its exact version.
How to install
mdr add fabiandistler/agents/problem-first-explanation@sha256:9aa4ac7a77cf4e11The line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_dgjmaxikcmrvc2la)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 28, 2026 and Oct 22, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0 latest | 2026-10-22 | e7a86a8 | 5,449 B | A | view · diff |
| v1.0 | 2026-10-21 | 9ffdcb0 | 5,478 B | A | view · diff |
| v1.0 | 2026-09-28 | 1c2b0d0 | 5,501 B | A | view · diff |
| v1.0 | 2026-09-28 | fe68628 | 5,377 B | A | view · diff |
| git:20260928.64a1b34 | 2026-09-28 | 64a1b34 | 6,177 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5449 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
fabiandistler/agents · 2 stars · license none declared · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dgjmaxikcmrvc2la GET https://markdownregistry.com/api/v1/resolve?ref=fabiandistler/agents/problem-first-explanation GET https://markdownregistry.com/api/v1/blob/9aa4ac7a77cf4e11e3b702f4a91b027b598ff2fa97bbdfaa839026b537456a4c
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.