how SKILL.md skillA
how from creedants/pstack-t3 is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add creedants/pstack-t3/how@git:20261011.042ae70Pins git:20261011.042ae70 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- creedants/pstack-t3
- Path
skills/how/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261011.042ae70, committed Oct 11, 2026
- First version recorded
- Oct 3, 2026
- Size
- 3,141 bytes
- Repository stars
- 15
- License
- MIT
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
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
# How Read [the pstack-t3 runtime](../pstack-runtime/SKILL.md) before spawning workers, choosing models, scheduling, or isolating work. It maps those steps onto T3's orchestrator tools. Explore the codebase to answer "how does X work?" questions. Produce architectural explanations at the level of a senior engineer onboarding onto a subsystem, enough to build a working mental model, not so much that it reads like annotated source code. Every spawn is a `delegate_task` child task with `mode: "async"`, a stable `clientRequestId` such as `how-<slug>-<angle>`, and a read-only brief. The prompt templates tell the child not to edit files, commit, or push. Explorers use the `how explorer` role with `role` set to `"research"`, and every explainer uses the `how explainer` role with `role` set to `"general"`. Resolve each role per [the runtime's Roles section](../pstack-runtime/SKILL.md#roles) with `python3 <pstack-runtime>/scripts/roles.py show --cwd "$PWD" --parent "<inheritedProviderInstanceId>/<inheritedModel>" --role "<role>"`. Set `target` to the role's seat. Leave `target` unset when the seat is `inherit`. If `delegate_task` rejects a target, apply the runtime's fallback and say… …
Read the whole file at its exact version.
How to install
mdr add creedants/pstack-t3/how@sha256:ed37c3837c188c03The line at the top of this page pins the label git:20261011.042ae70, 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_h5xkw7ogdonbgexr)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 3, 2026 and Oct 11, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261011.042ae70 latest | 2026-10-11 | 042ae70 | 3,141 B | A | view · diff |
| git:20261008.31a131d | 2026-10-08 | 31a131d | 3,592 B | A | view · diff |
| git:20261007.a59be7f | 2026-10-07 | a59be7f | 3,436 B | A | view · diff |
| git:20261003.ad880e0 | 2026-10-03 | ad880e0 | 3,429 B | A | view · diff |
| git:20261003.a632f62 | 2026-10-03 | a632f62 | 3,371 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 (3141 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
creedants/pstack-t3 · 15 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_h5xkw7ogdonbgexr GET https://markdownregistry.com/api/v1/resolve?ref=creedants/pstack-t3/how GET https://markdownregistry.com/api/v1/blob/ed37c3837c188c03f764f60800a3623475da1232ba6989335e59d3cf3aaf6958
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 creedants/pstack-t3
Every file in creedants/pstack-t3