resolving-stack-commands SKILL.md skillA
resolving-stack-commands from sebastiendegodez/skraft-plugin is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sebastiendegodez/skraft-plugin/resolving-stack-commands@git:20261011.2406fc7Pins git:20261011.2406fc7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sebastiendegodez/skraft-plugin
- Path
plugins/skraft-framework/skills/resolving-stack-commands/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261011.2406fc7, committed Oct 11, 2026
- First version recorded
- Aug 6, 2026
- Size
- 5,360 bytes
- Repository stars
- 12
- License
- GPL-3.0
Use whenever an agent must run a toolchain command (build, test, mutation) and needs the concrete invocation. Resolves build/test/mutation commands from the detected stack via the `quality-gates-<tech>` adapters so no agent hardcodes `dotnet test`, `dotnet build`, or any toolchain command. Loaded by acceptance-designer and software-engineer.
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
# Resolving Stack Commands (stack-agnostic) The single place that maps a repository's stack to its concrete toolchain commands (build, test, mutation). No agent and no workflow step may hardcode a command (`dotnet test`, `dotnet build`, `mvn test`, `pytest`, ...). They resolve it here instead. ## Why this exists The pipeline must run with .NET today and other stacks tomorrow (Java planned, not yet supported). If each agent embeds `dotnet test`, swapping or adding a stack means editing every agent. Centralizing the mapping keeps agents tech-agnostic: they say "build the solution" / "run the test suite" / "run mutation", this skill says how. ## Detection → adapter Detect the stack from markers at the repo root, then resolve the concrete commands from the matching `quality-gates-<tech>` adapter (the adapter owns the build / test / mutation commands and their evidence mapping): | Stack | Detection markers | Adapter | Status | |---|---|---|---| | .NET | `*.sln`, `*.slnx`, `**/*.csproj`, `Directory.Packages.props` | `quality-gates-dotnet` (`dotnet build` / `dotnet test` / `dotnet stryker`) | supported | …
Read the whole file at its exact version.
How to install
mdr add sebastiendegodez/skraft-plugin/resolving-stack-commands@sha256:fa5872478f84db00The line at the top of this page pins the label git:20261011.2406fc7, 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_myhn23qg3uqwy5pu)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Aug 6, 2026 and Oct 11, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261011.2406fc7 latest | 2026-10-11 | 2406fc7 | 5,360 B | A | view · diff |
| git:20261009.700b6e2 | 2026-10-09 | 700b6e2 | 5,504 B | A | view · diff |
| git:20261008.193dd3e | 2026-10-08 | 193dd3e | 4,940 B | A | view · diff |
| git:20260930.b9fa6cd | 2026-09-30 | b9fa6cd | 4,663 B | A | view · diff |
| git:20260925.778348a | 2026-09-25 | 778348a | 3,376 B | A | view · diff |
| git:20260806.b506b65 | 2026-08-06 | b506b65 | 2,452 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 (5360 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
sebastiendegodez/skraft-plugin · 12 stars · license GPL-3.0 · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_myhn23qg3uqwy5pu GET https://markdownregistry.com/api/v1/resolve?ref=sebastiendegodez/skraft-plugin/resolving-stack-commands GET https://markdownregistry.com/api/v1/blob/fa5872478f84db00c26aec0104f6c715f1074a69b23dcdffb8d84ada406f528c
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.