recall SKILL.md skillA
recall from mubit-ai/plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mubit-ai/plugins/recall@git:20260903.008c305Pins git:20260903.008c305 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mubit-ai/plugins
- Path
integrations/claude-code/skills/recall/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260903.008c305, committed Sep 3, 2026
- First version recorded
- Aug 15, 2026
- Size
- 2,383 bytes
- Repository stars
- 4
- License
- Apache-2.0
Search Mubit memory for lessons, rules, facts or past work; use when the injected memory is not enough.
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
Relevant memory was **already injected** at the top of this turn by the Mubit recall hook. Read it before searching. Most of the time you do not need this skill. When you do: 1. Issue **one** broad `mubit_recall` call. Not three narrow ones. 2. Read the evidence. If it answers the question, stop. 3. Only if the first call returned nothing usable, issue one reformulated call. Never fan out into parallel searches across sub-topics. Mubit retrieval is hybrid (semantic + lexical + recency + graph); one well-formed query beats four keyword slices at a quarter of the latency. Two calls is the ceiling. Cite what you use by its `reference_id`, and call `mubit_outcome` with those `entry_ids` when recalled memory turns out to be right or wrong. That feedback is what makes the next recall better. ## Writing the query Query with the *question*, not with keywords. "Why does the drain hook retry twice on a 5xx" retrieves better than "drain retry 5xx", because the semantic half of the hybrid index has something to match on and the lexical half still catches the identifiers. Include the identifiers you already know — file names, symbol names, error strings — inside the …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_gxr7qslgqc2gzzwd/4acdd2457c98f838d041b80fcb77120110fe7bf8052235f5219716cf9e9c28ee.json
Then /plugin install recall@markdownregistry-gxr7qslgqc2gzzwd in Claude Code. It installs git:20260903.008c305, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add mubit-ai/plugins/recall@sha256:4acdd2457c98f838The line at the top of this page pins the label git:20260903.008c305, 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_gxr7qslgqc2gzzwd)
6 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in mubit-ai/plugins/recall since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of recall from somewhere else? Ask it: where did my recall come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 2 versions of this file, between Aug 15, 2026 and Sep 3, 2026, about one every 19 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260903.008c305 latest | 2026-09-03 | 008c305 | 2,383 B | A | view · diff |
| git:20260815.5914984 | 2026-08-15 | 5914984 | 2,448 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/recall/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (2383 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
mubit-ai/plugins · 4 stars · license Apache-2.0 · pushed 2026-09-29 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gxr7qslgqc2gzzwd GET https://markdownregistry.com/api/v1/resolve?ref=mubit-ai/plugins/recall GET https://markdownregistry.com/api/v1/blob/4acdd2457c98f838d041b80fcb77120110fe7bf8052235f5219716cf9e9c28ee
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 mubit-ai/plugins
Every file in mubit-ai/plugins