problem-solver skillA
problem-solver is agent-read markdown (skill) from tronghieu/agent-skills: Diagnose problems before solving them: turn "X is broken and we don't know why" into a precise problem statement, verified root causes, solutions traced to those causes, and a rollout plan. Use whenever the user reports something failing, breaking, slowing, or recurring without a known cause: "sales dropped and we don't know why", "this keeps happening", "why does X keep failing", "find the root cause", "run a post-mortem", "5 whys"; Vietnamese "sao cứ bị vậy hoài", "tìm nguyên nhân gốc", "X đan.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Problem Solver A **diagnosis-first facilitator** for problems whose cause is unknown or unverified. The skill does two jobs that reinforce each other: 1. **Find the real cause.** Structured framing, boundary analysis, and root-cause methods matched to the shape of the problem — so the fix targets structure, not symptoms. 2. **Never fabricate.** You cannot see the user's systems, org, or data. Facts come from the user; everything else is a labeled hypothesis with a test attached. A tidy cause chain with invented links is worse than an honest incomplete one — it sends the user off to fix the wrong thing with full confidence. The second job is the signature. Any capable model can produce a plausible root-cause analysis; plausible is exactly the danger. What separates diagnosis from storytelling is the discipline below. ## The evidence discipline Three sources of truth run through every phase: - **Facts** — things the user states from direct knowledge, or data and artifacts they show you. Only these earn the label `[verified]`. - **Hypotheses** — candidate causes and links. These can come from you …
Read the whole file at its exact version.
How to install
mdr add tronghieu/agent-skills/problem-solver@git:20260905.623c278mdr add tronghieu/agent-skills/problem-solver@sha256:cb061ea230930b15Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_bky25iteblxmnw6q)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260905.623c278 latest | 2026-09-05 | 623c278 | 15,537 B | A | view · diff |
| git:20260718.5597285 | 2026-07-18 | 5597285 | 16,238 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 (15537 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
tronghieu/agent-skills · 72 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bky25iteblxmnw6q GET https://markdownregistry.com/api/v1/resolve?ref=tronghieu/agent-skills/problem-solver GET https://markdownregistry.com/api/v1/blob/cb061ea230930b155006d05fe23c06f9036fa44030a24e972a90eea1a49c21c9
Your agent 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.