recall SKILL.md skillA
recall 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/recall@git:20261014.216b9fbPins git:20261014.216b9fb 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/recall/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261014.216b9fb, committed Oct 14, 2026
- First version recorded
- Oct 3, 2026
- Size
- 6,551 bytes
- Repository stars
- 15
- License
- MIT
Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.
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
# Recall 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. **Before you start or resume work, you rebuild the user's recent working context and hand back a tight capsule of where things stand now and what to do next.** Keep it tight and on-topic. Read only what the in-scope threads need, then stop. Your context lives in two records. Your own chat history holds what you did and decided. The shared record holds everything that happened around the same code under other names: the symptoms users keep reporting, the fixes that shipped and got reverted, the errors still firing in prod. That second record is what the **why** skill searches, across source control, the issue tracker, chat and issue channels, long-form docs, and error tracking. A feature with a long bug tail keeps most of its story there, so don't reconstruct it from your threads alone. …
Read the whole file at its exact version.
How to install
mdr add creedants/pstack-t3/recall@sha256:c379385f451c8f98The line at the top of this page pins the label git:20261014.216b9fb, 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_c6kisix73h2y33z4)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Oct 3, 2026 and Oct 14, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.216b9fb latest | 2026-10-14 | 216b9fb | 6,551 B | A | view · diff |
| git:20261008.31a131d | 2026-10-08 | 31a131d | 6,496 B | A | view · diff |
| git:20261003.a632f62 | 2026-10-03 | a632f62 | 6,340 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 (6551 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_c6kisix73h2y33z4 GET https://markdownregistry.com/api/v1/resolve?ref=creedants/pstack-t3/recall GET https://markdownregistry.com/api/v1/blob/c379385f451c8f98ec9fcaf0e477a75b352ddcfa6bfa65a48f374e24931d510f
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