agentleFS
vidit19sharmavidit19sharma/neogents/skills/recall/SKILL.md

recall

Skill1 starsChanged 12 days agoMITView on GitHub

Search everything the project remembers — the second brain, plan artifacts, and the run ledger — with plain grep, returning file:line pointers. Use when the user asks "did we already...", "when did we decide...", "what did the review say about...", or before re-exploring something a past session may have answered.

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

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 129 edited versions we read keep these.

  • 0

    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
  1. Very specific:

    Answer from pointers: Read only the files the hits point at, then answer citing file:line for every claim.

    line 24

“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

/neo:recall — grep project memory

Memory on disk: !du -sh .neo 2>/dev/null || echo "no .neo — run /neo:init"

Past sessions already paid for this knowledge. Search it before re-earning it with fresh recon.

Steps

  1. Guard: no .neo/ → suggest /neo:init and stop.
  2. Derive terms from the user's question — 1 to 3 of them. Exact identifiers (file names, function names, error strings) beat prose. Try the most specific term first.
  3. Search (one command per term):
    grep -rin -- "<term>" .neo/brain .neo/plans .neo/runs 2>/dev/null | head -40
    Too noisy → tighten the term or add -w. Zero hits → loosen it (stem the word, drop qualifiers).
  4. Answer from pointers. Read only the files the hits point at, then answer citing file:line for every claim. Prefer the newest hit when sources disagree — and say so.
  5. Nothing found → say memory has nothing on it and fall back to normal recon. Never present absence of memory as absence of fact.

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.