agentleFS
jmylchreestjmylchreest/aide/skills/recall/SKILL.md

recall

Skill19 starsChanged 3 months agoMITView on GitHub

Search memories and decisions to answer questions about past learnings, choices, and context

142 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-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

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 6 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 129 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search stored memories and decisions to answer questions about past learnings, architectural choices, patterns, and project context.

    line 19
  2. Very specific:

    Use mcp__plugin_aide_aide__memory_search with relevant keywords

    line 42
  3. Very specific:

    Use mcp__plugin_aide_aide__decision_get with the topic, or mcp__plugin_aide_aide__decision_list

    line 43
  4. Distinctive:

    Analyze timestamps: - Prefer most recent (ULIDs are time-ordered)

    line 44
  5. Distinctive:

    When the user asks about previous context:

    line 49
  6. Very specific:

    Use mcp__plugin_aide_aide__decision_get with topic (e.g., "testing")

    line 52
  7. Very specific:

    If unsure of topic name, use mcp__plugin_aide_aide__decision_list

    line 53
  8. Very specific:

    Use mcp__plugin_aide_aide__memory_search with query (e.g., "ESM imports")

    line 56
  9. Distinctive:

    If no results found:

    line 79
  10. Distinctive:

    Try alternative terms: - search with synonyms or related keywords

    line 81
  11. Very specific:

    Broaden the search: - use mcp__plugin_aide_aide__memory_list to browse all memories

    line 82
  12. Distinctive:

    Always prefer the most recent when there are conflicts

    line 90

“Common” is measured: kept by at least 6 in 10 of the 129 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Recall

Recommended model tier: balanced (sonnet) - this skill performs straightforward operations

Search stored memories and decisions to answer questions about past learnings, architectural choices, patterns, and project context.

MCP Tools

Search Memories

ToolPurpose
mcp__plugin_aide_aide__memory_searchFull-text search (fuzzy, prefix, substring matching)
mcp__plugin_aide_aide__memory_listList memories, optionally filtered by category

Get Decisions

ToolPurpose
mcp__plugin_aide_aide__decision_getGet specific decision by topic
mcp__plugin_aide_aide__decision_listList all decisions
mcp__plugin_aide_aide__decision_historyGet all versions of a decision

Workflow

  1. Parse the question - Extract key terms
  2. Search both sources:
    • Use mcp__plugin_aide_aide__memory_search with relevant keywords
    • Use mcp__plugin_aide_aide__decision_get with the topic, or mcp__plugin_aide_aide__decision_list
  3. Analyze timestamps - Prefer most recent (ULIDs are time-ordered)
  4. Answer - Combine relevant context from both sources

Instructions

When the user asks about previous context:

  1. For architectural/design questions (testing, auth, database, etc.):
    • Use mcp__plugin_aide_aide__decision_get with topic (e.g., "testing")
    • If unsure of topic name, use mcp__plugin_aide_aide__decision_list
  2. For learnings/patterns/gotchas:
    • Use mcp__plugin_aide_aide__memory_search with query (e.g., "ESM imports")
  3. When answering:
    • Cite the source (memory or decision)
    • Include the date for context
    • Note if something was updated/changed

Examples

User: "What testing framework did we decide on?" → Use mcp__plugin_aide_aide__decision_get with topic="testing" → Answer with the decision and rationale

User: "What was the issue with ESM imports?" → Use mcp__plugin_aide_aide__memory_search with query="ESM imports" → Answer with the learning

User: "What approach did we take for auth?" → Use both mcp__plugin_aide_aide__decision_get (topic="auth") and mcp__plugin_aide_aide__memory_search (query="auth") → Combine both sources in answer

Failure Handling

If no results found:

  1. Try alternative terms - search with synonyms or related keywords
  2. Broaden the search - use mcp__plugin_aide_aide__memory_list to browse all memories
  3. Report clearly: "No memories or decisions found for '<topic>'. This may not have been recorded previously."

Notes

  • This skill is READ-ONLY - searches but doesn't modify
  • Decisions are structured (topic → decision + rationale)
  • Memories are freeform learnings, gotchas, patterns
  • Always prefer the most recent when there are conflicts

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.