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
**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 transcripts alone.
…
The line at the top of this page pins the label git:20260923.11fd787, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_awokcqcphd27j3jf
GET https://markdownregistry.com/api/v1/resolve?ref=lucasheriques/pstack/recall
GET https://markdownregistry.com/api/v1/blob/ba0c3855b9b373f7807996bac3cd3b9dcaceb6a1537d01b2ea24b1d4290f4524
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.
lucasheriques/pstack · .claude/skills/sync-upstream/SKILL.md · Merge the latest cursor/plugins pstack into this Claude Code port. Use for "sync upstream", "update pstack from…
lucasheriques/pstack · skills/architect/SKILL.md · Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use…
lucasheriques/pstack · skills/arena/SKILL.md · Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for…
lucasheriques/pstack · skills/automate-me/SKILL.md · Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a…
lucasheriques/pstack · skills/benchmark-checklist/SKILL.md · Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened)…
lucasheriques/pstack · skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
lucasheriques/pstack · skills/correct/SKILL.md · Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types…
lucasheriques/pstack · skills/create-verification-skill/SKILL.md · Generate a project-local verification skill that drives your app the way a user does — any language, framework, or…
lucasheriques/pstack · skills/figure-it-out/SKILL.md · Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a…
lucasheriques/pstack · skills/how/SKILL.md · Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions…
cursor/plugins · harness/pstack/claude-code/skills/recall/SKILL.md · Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports…
cursor/plugins · pstack/skills/recall/SKILL.md · Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports…
michael-denyer/pstack-claude · plugins/pstack/skills/recall/SKILL.md · Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports…
backnotprop/pstack · skills/recall/SKILL.md · Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports…
indranilbanerjee/digital-marketing-pro · skills/recall/SKILL.md · Recall past learnings for a channel or audience as a confidence-ranked playbook. "what worked last time"
snowflake-labs/cocoplus · .cortex/skills/cocorecall/recall/SKILL.md · CocoPod session history retrieval — a local SQLite index over past session transcripts, enabling precision retrieval at…
oliver-kriska/claude-elixir-phoenix · plugins/elixir-phoenix/skills/recall/SKILL.md · Recall prior work from past sessions — how a bug was fixed, what was decided, where a pattern lives. Use when asked…
agenttoolkit/altk-evolve · platform-integrations/claw-code/plugins/evolve-lite/skills/evolve-lite/recall/SKILL.md · Must be used at the start of any non-trivial task involving code changes, debugging, repo exploration, file inspection…
