Recall
Agent skills, autonomous agents, and MCP-companions for programming
npx -y skills add DROOdotFOO/agent-skills --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
- 1 stars1 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
Query the recall knowledge base for relevant context. Searches decisions, patterns, gotchas, links, and insights stored across sessions. TRIGGER when: user asks to "recall", "remember", "what did we decide about", "check knowledge base", or references past decisions/patterns. DO NOT TRIGGER when: user is talking about memory/recall in a general sense, or working on the recall agent code itself.
SKILL.md
2.4 KB, as published. Nobody here has run it
Recall
Query and store knowledge entries (decisions, patterns, gotchas, links, insights) in a local SQLite database with full-text search.
CLI Usage
# Add entries
recall add "Always quote FTS5 tokens containing hyphens" --type gotcha --project recall --tags sqlite,fts5
recall add "Use WAL mode for concurrent reads" --type pattern --project myproj
# Search (full-text, with optional filters)
recall search "sqlite"
recall search "architecture" --project myproj --type decision
# List, get, delete, stats
recall list --project recall --limit 10
recall get 1
recall delete 1
recall stale --days 90
recall stats
Entry Types
| Type | Use for |
|---|---|
decision | Architectural or design decisions with rationale |
pattern | Reusable approaches or techniques |
gotcha | Non-obvious pitfalls or footguns |
link | External resources worth remembering |
insight | General observations or learnings (default) |
When to Use
- Before making architectural decisions, search for prior decisions on the topic
- After resolving a tricky bug, store the gotcha for future reference
- When encountering a useful pattern, capture it with project and tags
- When finding a valuable resource, save it as a link entry
What You Get
- Full CLI and MCP tool reference for querying and storing knowledge entries (decisions, patterns, gotchas, links, insights)
- Entry type guidance so you store knowledge in the right category for later retrieval
- Search and filtering patterns for finding relevant past context by project, type, or full-text query
Reference
| File | Topic |
|---|---|
| mcp-setup.md | MCP server config, tools, storage, install |
Gives 0 of the 12 instructions most memory context skills give
Counted across 674 of the 847 authors here whose files we hold, read 2026-08-06
- inform the user when setup is completein 21 of 674, across 6 files
- confirm the draft with the user before writingin 21 of 674, across 6 files
- update the agent skills block in place if it existsin 21 of 674, across 6 files
- present findings to the userin 20 of 674, across 5 files
- write the three docs files from seed templatesin 20 of 674, across 5 files
- ask the user about each decision one at a timein 19 of 674, across 4 files
- edit CLAUDE.md if it existsin 18 of 674, across 3 files
- explore current repo statein 18 of 674, across 3 files
- do not overwrite user edits to surrounding sectionsin 18 of 674, across 3 files
- back up the original file before overwritingin 16 of 674, across 8 files
- keep the memory index under 200 linesin 15 of 674
- Provide actionable steps and verificationin 13 of 674, across 2 files
Said here and by no other author read
- search for prior decisions before architectural choices
- store gotchas after resolving tricky bugs
- capture useful patterns with project and tags
- save valuable resources as link entries
- filter search results by project or type
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.