recall
Skill4 starsChanged 14 days agoMITView on GitHub
Use when Taimoor asks what he or the vault knows about a topic, wants a researched answer from the mind database, or says "recall X" / "what do we know about X". Searches the Tesseract vault, synthesizes a cited answer, and files it into Claude/Answers/ so knowledge compounds.
150 other projects use a version of this.
Adopted by
Most recently taken up by
- gfunc/skillstheir own version, first seen Nov 16, 2026
- shiwenbin1617/pstacktheir own version, first seen Nov 16, 2026
- muhammademanaftab/pulsetheir own version, first seen Nov 15, 2026
- backnotprop/pstacktheir own version, first seen Nov 15, 2026
- sammyjoyce/prime-pstacktheir own version, first seen Nov 15, 2026
- upamune/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use addskill, apply-firmware and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ryanportfolioSkilladdskill
Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.
Also in 6 projects that use this
ryanportfolioSkillapply-firmware
Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.
Also in 6 projects that use this
- +10 more from ryanportfolio
Other versions150 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 150
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- backnotprop/pstack★ 4.2ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- indranilbanerjee/digital-marketing-pro★ 934same name
- ArtemXTech/personal-os-skills★ 545same name
- entireio/skills★ 240same name
- termdock/termdock-issues★ 160same name
140 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 137 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Citation-or-label: Every factual claim either cites its source note as a [[wikilink]], or is explicitly marked *(not from the vault)*.
- Distinctive: line 15
Thin retrieval → say so: If the vault has little on the topic, report that honestly and STOP.
- Distinctive: line 18
Always end with a "What the vault doesn't know" section.
“Common” is measured: kept by at least 6 in 10 of the 137 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Recall — researched Q&A over the Tesseract vault
Answer the question from the vault, cite every claim, file the answer.
Requires the tesseract MCP server.
Contract (non-negotiable)
- Citation-or-label. Every factual claim either cites its source note
as a
[[wikilink]], or is explicitly marked (not from the vault). - Thin retrieval → say so. If the vault has little on the topic, report that honestly and STOP. Never pad an answer with model knowledge dressed up as vault knowledge. No answer note is filed in that case.
- Always end with a "What the vault doesn't know" section.
Steps
context_bundle(question, limit=10)— hybrid hits + graph entities + related notes in one call.- Judge coverage: are at least 2 hits genuinely about the question? If
not: tell Taimoor the vault has almost nothing on this, list the nearest
misses, offer to
capturethe question oradd_taska research follow-up, and stop here. read_notethe top 3–5 relevant hits IN FULL — the bundle's excerpts locate notes, they are not enough to synthesize from. Follow one or tworelated_noteschains if they add real context.- Compose the answer with exactly this structure:
## Answer— synthesized, every claim carrying a[[wikilink]].## Sources— bullet list of every cited note.## What the vault doesn't know— gaps, contradictions, staleness.
- Offer to file each gap as a task (
add_task) or a capture — the gaps are tomorrow's ingest queue. - File the answer with
write_note:- Path:
Claude/Answers/YYYY-MM-DD <question slug>.md— slug is the question compressed to at most 6 words with the characters\ / : * ? " < > | [ ] # ^stripped. If the path already exists, suffix2,3, … (same rule as session notes). - Frontmatter (YAML):
created: YYYY-MM-DD HH:MM,agent: claude,project: <if obvious, else "">,tags: [answer],type: answer,question: "<the exact question asked>". - Body: the three sections from step 4.
- Path:
- Show the full answer in chat as well — the note is for the vault, the chat reply is for now.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

