recall SKILL.md skillA
recall from jeongjaesoon/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jeongjaesoon/agent-skills/recall@git:20261026.46adf36Pins git:20261026.46adf36 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jeongjaesoon/agent-skills
- Path
skills/recall/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261026.46adf36, committed Oct 26, 2026
- First version recorded
- Sep 24, 2026
- Size
- 5,607 bytes
- Repository stars
- 3
- License
- MIT
Rebuild recent working context from past sessions, live state and the shared record (tracker, PRs, worklogs) into a short current-state brief. Use for "어디까지 했지", "이번 주에 뭐 했지", 'catch me up', or resuming work in a fresh or restarted session. A status report on work in flight is brief.
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, 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. Context lives in two records. Past sessions hold what was done and decided. The shared record holds everything that happened around the same code under other names: tickets, PRs that shipped and got reverted, symptoms users keep reporting, worklogs. That second record is what the **why** skill searches. A feature with a long bug tail keeps most of its story there, so don't reconstruct it from transcripts alone. ## Where past sessions live Claude Code writes each session to `~/.claude/projects/<dir>/<session-id>.jsonl`, where `<dir>` is the session's working directory with every `/` and `.` replaced by `-`. One JSON object per line. Orca cards each run in their own worktree, so one repo's history spans many `<dir>`s: its main checkout, every path in `git worktree list`, and cards already removed, whose `<dir>` starts with the encoded parent folder of the repo's worktrees (for Orca, `~/orca/workspaces/<repo>/`). …
Read the whole file at its exact version.
How to install
mdr add jeongjaesoon/agent-skills/recall@sha256:5bbbabf8024728f2The line at the top of this page pins the label git:20261026.46adf36, 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_usjdubz3ycmg4zyl)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 24, 2026 and Oct 26, 2026, about one every 8 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.46adf36 latest | 2026-10-26 | 46adf36 | 5,607 B | A | view · diff |
| git:20261012.14c3b4f | 2026-10-12 | 14c3b4f | 5,617 B | A | view · diff |
| git:20260925.f7829f3 | 2026-09-25 | f7829f3 | 5,742 B | A | view · diff |
| git:20260924.41ba201 | 2026-09-24 | 41ba201 | 5,549 B | A | view · diff |
| git:20260924.d7423e0 | 2026-09-24 | d7423e0 | 5,227 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 (5607 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
jeongjaesoon/agent-skills · 3 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_usjdubz3ycmg4zyl GET https://markdownregistry.com/api/v1/resolve?ref=jeongjaesoon/agent-skills/recall GET https://markdownregistry.com/api/v1/blob/5bbbabf8024728f29efa88c47adec893905667d82e34c0c19dc45751ca57c6f5
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 jeongjaesoon/agent-skills
Every file in jeongjaesoon/agent-skills