setup-diagnosis SKILL.md skillA
setup-diagnosis from sigistry/marketplace is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sigistry/marketplace/setup-diagnosis@git:20260826.571bc2fPins git:20260826.571bc2f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sigistry/marketplace
- Path
plugins/codebase-navigator/skills/setup-diagnosis/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260826.571bc2f, committed Aug 26, 2026
- First version recorded
- Jul 15, 2026
- Size
- 3,647 bytes
- Repository stars
- 3
- License
- MIT
This skill should be used when the user mentions "setup", "getting started", "install dependencies", "dev environment", "onboarding", "won't run", "version mismatch", "devcontainer", "env vars", "works on my machine", or a failing local install/build. It maps where a repo declares its runtime needs and how to diagnose and fix the common setup failures that block a green build on day one.
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
# Setup Diagnosis ## Purpose The biggest day-one sink is getting a green build: missing dependencies, the wrong runtime version, OS-specific breakage, missing env vars, and silently outdated README steps. This skill provides two things, a **map of where a repo declares what it needs** (so you stop guessing) and a **catalog of the common failure modes and their fixes**: so bootstrapping becomes detect → run → diagnose → verify, not trial and error. ## Principle: read the declared requirements, don't guess A repo almost always tells you what it needs, in machine-readable files. Trust those over prose READMEs, which drift. Reconcile pins across files before running anything. ## Where requirements live (quick map) | Need | Look in | |------|---------| | Runtime version | `.nvmrc`, `.tool-versions`, `mise.toml`, `.python-version`, `.ruby-version`, `engines`, `go.mod`, `<java.version>` | | Package manager | `packageManager` field, lockfile kind, `Gemfile`/`poetry.lock`/`Pipfile.lock` | | Dependencies | `package.json`, `pyproject.toml`/`requirements*.txt`, `Gemfile`, `go.mod`, `pom.xml`/`build.gradle`, `Cargo.toml` | …
Read the whole file at its exact version.
How to install
mdr add sigistry/marketplace/setup-diagnosis@sha256:ec5ce23dd08be2b1The line at the top of this page pins the label git:20260826.571bc2f, 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_243e3embqvbkxsrd)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jul 15, 2026 and Aug 26, 2026, about one every 42 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260826.571bc2f latest | 2026-08-26 | 571bc2f | 3,647 B | A | view · diff |
| git:20260715.6169119 | 2026-07-15 | 6169119 | 3,647 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 (3647 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
sigistry/marketplace · 3 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_243e3embqvbkxsrd GET https://markdownregistry.com/api/v1/resolve?ref=sigistry/marketplace/setup-diagnosis GET https://markdownregistry.com/api/v1/blob/ec5ce23dd08be2b102392471d27ba7d4cc9dfa29e8fe028a9075e080700138b0
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.