stack-detection skillA
stack-detection is agent-read markdown (skill) from nahid-sparktales/agent-dispatcher: Establish what a frontend project actually uses — framework, router, package manager, styling, component layer, TypeScript posture — from package.json, lockfiles, config files and the source itself, before loading framework-specific guidance or writing a line of code. Fires at the start of any frontend task in an unfamiliar or half-remembered repo, and whenever you are about to assume a convention. Not for choosing a stack for a new project, and not a substitute for reading the code you are abou.
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
# Stack detection Most wrong frontend edits are correct code for a stack the project does not use. Detection is cheap; guessing is not. ## When this fires Before the first edit in a frontend repo you have not already mapped in this session, and again whenever you catch yourself about to say "this project probably uses". It does not fire for a repo whose conventions you have already read this session. ## Procedure 1. **Find the right `package.json` first.** In a monorepo the root one describes the workspace, not the app. Locate the nearest `package.json` above the file you are changing, and note whether a root one also exists — dependencies can be hoisted, tooling config usually is. 2. **Read dependencies and scripts together.** `dependencies` and `devDependencies` say what is installed; `scripts` say what is actually run. The dev, build and test commands are the ones to use later — do not invent `npm run dev` if the project spells it differently. 3. **Get real versions from the lockfile, not the range.** `^15.0.0` in `package.json` is a constraint. The lockfile (`package-lock.json`, `pnpm-lock.yaml`, `yarn.lock`, `bun.lock*`) holds …
Read the whole file at its exact version.
How to install
mdr add nahid-sparktales/agent-dispatcher/stack-detection@git:20260919.a0d4f55mdr add nahid-sparktales/agent-dispatcher/stack-detection@sha256:ef6dfbbccb0f61c1Pin 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_wop7in2hgg5zyun6)
1 badge views in 30 days
Versions
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 (6190 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
nahid-sparktales/agent-dispatcher · 49 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wop7in2hgg5zyun6 GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/stack-detection GET https://markdownregistry.com/api/v1/blob/ef6dfbbccb0f61c13336823baeda833d929639ce43c77aa3d8c2745a7a32c501
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.