recall
Skill4 starsChanged 4 months agoMITView on GitHub
Answer any question about you, your business, the market, or a past decision from your co-brain — with exact verbatim citations back to `sources/`. Flow - grep `INDEX.md` → read the candidate notes → re-verify each `src` quote against its source → answer with citations. Refuses to fabricate: if it isn't sourced, it says so plainly and offers to `/capture` the gap. Triggers - any factual/business question, "recall", "what does my brain say", "what did I decide about X", "who is Y", "what do I know about Z".
151 other projects use a version of this.
Adopted by
Most recently taken up by
- GoBeromsu/craft-skillstheir own version, first seen Nov 16, 2026
- gfunc/skillstheir own version, first seen Nov 16, 2026
- DeepExtrema/Tesseracttheir 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
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 versions151 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 151
- 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
141 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.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms-full.txtllms.txt
- llms.txtllms.txt
- agents-syncSkill
- call-agentSkill
- captureSkill
- context-restoreSkill
- context-saveSkill
- curatorSkill
- learnSkill
- onboardSkill
- reviewSkill
- skillifySkill
- wiki-doctorSkill
- worklog-audioSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 138 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Read the shortlisted wiki/ note bodies.
- Distinctive: line 33
If two notes contradict, surface BOTH and say it's unresolved — don't paper over it.
- Very specific: line 36
If no sourced note answers the question, say so plainly: "Nothing sourced in the wiki covers this." Then offer leads — the closest wiki/ …
- Distinctive: line 42
No verifiable source → no asserted fact.
“Common” is measured: kept by at least 6 in 10 of the 138 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
Inherits
references/kernel.md(the provenance contract). Readsreferences/wiki-spec.mdfor schema.
The whole point of this skill: answers that are faster AND more accurate than you are from memory — with exact sources. An answer without a citation is a bug.
Execution
Step 1 — Find candidate notes (no body reads yet)
grepINDEX.md— the NOTES table, the ALIASES section, and the SUPERSEDED redirects — for keywords from the question. Aliases catch phrasing variance; superseded redirects stop you citing retired facts.- Shortlist the matching note ids. Follow any
superseded_byto the current note.
Step 2 — Read and re-verify
- Read the shortlisted
wiki/note bodies. - For each
srcblock you're about to rely on, re-verify the citation: resolvesourceviasources/_sources.mdto a path, then confirm thequotestill appears verbatim in that file. If the source file's hash drifted, re-check; if the quote no longer resolves, the note is stale — flag it, don't silently trust it (and suggest/wiki-doctor).
Step 3 — Answer
- Answer in your voice (see
references/voice.md/CLAUDE.md). Direct, concise, lead with the answer. - Every factual claim is followed by its citation. Format:
(source: <source-key>, "<short verbatim quote>", captured <date>)— and name thewiki/note id when useful. - Distinguish confidence honestly: "the source states…" (
stated) vs "I inferred from…" (inferred) vs "reportedly, per {{party}}…" (reported). For areportednote, keep the attribution visible — a third-party claim is never restated as your own fact. - If two notes contradict, surface BOTH and say it's unresolved — don't paper over it.
Step 4 — When the brain doesn't know
- If no sourced note answers the question, say so plainly: "Nothing sourced in the wiki covers this." Then
offer leads — the closest
wiki/notes, any relatedinbox/drafts (flagged as unsourced) — and an offer to run/captureto fill the gap. Never fabricate an answer or a citation to fill the silence.
Refusal rule
No verifiable source → no asserted fact. Surface the gap and the nearest leads instead. A confident, unsourced answer is the single worst failure mode this co-brain can produce.
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.

