investigate SKILL.md skillA
investigate from vraj-ai/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vraj-ai/skills/investigate@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vraj-ai/skills
- Path
standalone/investigate/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Oct 14, 2026
- Size
- 2,451 bytes
- Repository stars
- 3
- License
- MIT
Answer a read-only question about the codebase — a walk-through of how a subsystem, queue, endpoint, webhook, or request flow works, where a behavior comes from, what a change could break — from source and runtime evidence, returning file pointers and an honest confidence level instead of a prose dump. Use for "how does X work", "where does Y happen", "what calls Z", blast-radius questions, and any task whose first step is understanding rather than changing.
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 A read-only pass. The deliverable is a map with evidence, not an essay — and never a diff. ## Step 1 — Bound the question State the question in one line and what would answer it: a named entry point, a call chain, a data flow, the reason a decision was made. An investigation without a stated question becomes a tour of whatever was opened first. ## Step 2 — Follow the evidence, not the filename - Enter through the production entry point — the route handler, job, or callback real traffic uses — not the most central-looking file. - Read callers before implementations. Where a symbol is used matters more to the answer than how it is written inside. - Follow the actual call chain with grep and the harness's navigation; do not infer connections from naming similarity. - For "why was it built this way", the evidence is in git log, linked issues/PRs, ADRs, and comments — in that order of reliability. When the record is silent, say the record is silent. ## Step 3 — Check claims against the real thing Where the answer depends on runtime behavior, observe it: run the read-only command, query the table, hit the endpoint. Reading code tells you what it …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_onyxuj4enn25yt4p/789023882b1e67ab530ff5860119e646b986b93ccaf7460ba5c49caafff292b7.json
Then /plugin install investigate@markdownregistry-onyxuj4enn25yt4p in Claude Code. It installs v1.0.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add vraj-ai/skills/investigate@sha256:789023882b1e67abThe line at the top of this page pins the label v1.0.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_onyxuj4enn25yt4p)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in vraj-ai/skills/investigate since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of investigate from somewhere else? Ask it: where did my investigate come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Oct 14, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/investigate/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (2451 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
vraj-ai/skills · 3 stars · license MIT · pushed 2026-11-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_onyxuj4enn25yt4p GET https://markdownregistry.com/api/v1/resolve?ref=vraj-ai/skills/investigate GET https://markdownregistry.com/api/v1/blob/789023882b1e67ab530ff5860119e646b986b93ccaf7460ba5c49caafff292b7
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.