Recall
A workshop for accumulating build-taste across projects. Cross-tool dev brain (Claude Code, Cursor, Codex, Gemini).
npx -y skills add CloseTheLoops/moradin --skill recallAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Search memory and synthesize an answer with citations to source files.
SKILL.md
1.9 KB, 455 tokens by cl100k_base, as published. Nobody here has run it
moradin:recall
Search Moradin's memory and answer a question with citations.
When invoked
/moradin:recall <question>
or /moradin:recall <question> --topic <tag> for topic-filtered search.
What you do
-
Tokenize the question. Identify key terms.
-
Run BM25 search:
python scripts/search.py "<question>" [--topic <tag>] [--applies-to <tag>] --limit 10 -
Read the top results (typically 5-10 files). For each, read both frontmatter and body.
-
Synthesize an answer that:
- Directly addresses the question
- Cites EACH source file by path (e.g.
memory/patterns/closed_loop_eval.md) - Distinguishes between principles (universal rules), patterns (designs), references (external knowledge), and lessons (incident-derived)
- Honest about gaps: if memory doesn't have the answer, say so
-
Optional: file the synthesis back. If the synthesis itself is valuable, ask the operator: "This synthesis is valuable — file it back as a new pattern or lesson?"
Citation format
Always cite specific files. Don't say "your memory has principles about closed loops" — say "see memory/principles/close_every_loop.md."
Topic filter
If the operator's question is clearly within one topic (e.g. "what do I know about evals?"), use --topic eval to focus the search.
If unsure: search without filter first; let BM25 surface relevant docs.
Don't
- Don't synthesize without reading the actual files. Search results give you hits — read them before answering.
- Don't make up content. If the memory doesn't say it, say "memory doesn't cover this."
- Don't filter results silently. If you skip a hit, explain why.
Output
- A synthesized answer with file-path citations
- Optionally: a new file in
memory/patterns/ormemory/lessons/if the synthesis is filed back
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.