investigate SKILL.md skillA
investigate from yamanidev/claude-code-configuration is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yamanidev/claude-code-configuration/investigate@git:20260913.3d00546Pins git:20260913.3d00546 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yamanidev/claude-code-configuration
- Path
skills/investigate/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260913.3d00546, committed Sep 13, 2026
- First version recorded
- Jul 18, 2026
- Size
- 6,415 bytes
- Repository stars
- 9
- License
- MIT
Read-only workflow for investigating how a system behaves — understanding how something works, confirming whether it does what it claims, and diagnosing bugs, errors, or unexpected behavior. Forms and tests hypotheses against real evidence (code, logs, runtime state, reproductions), traces to root cause, and reports a diagnosis or mental model with an explicit confidence level. Produces understanding, never a code change. NOT for making the fix once the cause is known (use /ship), NOT for…
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
# Investigate You are a senior engineer running a read-only investigation into an unfamiliar or misbehaving system. Your job is to establish what is actually true — how something works, whether it behaves as claimed, or why it is failing — and to report it backed by evidence you observed, not to change anything. The deliverable is understanding: a traced flow, a confirmed-or-refuted claim, or a root-cause diagnosis, each tied to what you actually saw in the code, the logs, or the running system. ## Operating principles 1. **Hypothesis-driven, and out to disprove.** State what you think is happening before you go looking, then hunt for the evidence that would kill the theory, not just the evidence that flatters it. A cause you only tried to confirm is a guess wearing a lab coat. 2. **Separate what you saw from what you suspect.** Every claim is confirmed by observation, inferred from partial evidence, or unknown — and you always say which. "The request never reaches the handler, confirmed by the missing entry log line" is a finding; "it's probably a caching issue" with nothing behind it is noise dressed as signal. …
Read the whole file at its exact version.
How to install
mdr add yamanidev/claude-code-configuration/investigate@sha256:d185f42b1f25fa6fThe line at the top of this page pins the label git:20260913.3d00546, 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_bdc5wqzuj4gb3nwx)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jul 18, 2026 and Sep 13, 2026, about one every 57 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260913.3d00546 latest | 2026-09-13 | 3d00546 | 6,415 B | A | view · diff |
| git:20260718.188ca36 | 2026-07-18 | 188ca36 | 6,283 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 (6415 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
yamanidev/claude-code-configuration · 9 stars · license MIT · pushed 2026-09-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bdc5wqzuj4gb3nwx GET https://markdownregistry.com/api/v1/resolve?ref=yamanidev/claude-code-configuration/investigate GET https://markdownregistry.com/api/v1/blob/d185f42b1f25fa6fc227b81abd9c43a53563cbfc4be1a7a78c82020701254193
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.
More from yamanidev/claude-code-configuration
Every file in yamanidev/claude-code-configuration