needs-stack-mapping SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
needs-stack-mapping from devantler-tech/agent-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add devantler-tech/agent-plugins/needs-stack-mapping@git:20261101.7205f84Pins git:20261101.7205f84 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- devantler-tech/agent-plugins
- Path
plugins/vibe-coding/skills/needs-stack-mapping/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261101.7205f84, committed Nov 1, 2026
- First version recorded
- Jul 13, 2026
- Size
- 4,085 bytes
- Repository stars
- 3
- License
- Apache-2.0
Translate a non-technical person's plain-language product needs (an outcome, an audience, a workflow) into the deployment's technical building blocks behind the scenes, keeping the conversation entirely in the user's vocabulary. Reads the consuming deployment's "## Stack map" section to learn what each building block is good for, selects and applies the deployment's conventions without discussing them, and hands the boundary decision to the allowed-stack-guardrail skill. Use when assisting a…
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
# Needs → stack mapping
The person you are assisting describes what they want in the vocabulary of their product — an
outcome ("people should be able to book a session"), an audience ("my newsletter readers"), a
workflow ("when someone pays, send them the files"). Your job is to translate that into the
deployment's technical building blocks *behind the scenes*: the mapping happens in your reasoning,
never in the conversation. Conducted in the register of the `jargon-free-voice` skill.
## Where the building blocks come from
The allowed building blocks are **deployment-owned configuration, not part of this skill**: the
consuming deployment's canonical instructions file (`AGENTS.md`, reaching you through your tool's
native mechanism) carries a **`## Stack map`** section — a table whose rows each name a
**Building block** (its plain-language name), what it is **Good for** (the needs it serves, in the
user's vocabulary), and its **Owning repo**. That table is your entire menu:
- **Match needs against the *Good for* column.** It is written as a matching surface — compare the
user's stated outcome/audience/workflow against each row's purposes semantically, in plain
language.
…Read the whole file at its exact version.
How to install
mdr add devantler-tech/agent-plugins/needs-stack-mapping@sha256:99b3306d048e2c59The line at the top of this page pins the label git:20261101.7205f84, 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_ld7wpujxig7fvqt4)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jul 13, 2026 and Nov 1, 2026, about one every 112 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261101.7205f84 latest | 2026-11-01 | 7205f84 | 4,085 B | A | view · diff |
| git:20260713.e4186bc | 2026-07-13 | e4186bc | 4,271 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 (4085 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
devantler-tech/agent-plugins · 3 stars · license Apache-2.0 · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ld7wpujxig7fvqt4 GET https://markdownregistry.com/api/v1/resolve?ref=devantler-tech/agent-plugins/needs-stack-mapping GET https://markdownregistry.com/api/v1/blob/99b3306d048e2c59901bda00eb4872fee66d29e6fb920f25e5b342c72ee4f6df
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 devantler-tech/agent-plugins
Every file in devantler-tech/agent-plugins