agentleFS
Sign inStart free
qqq1212341qqq1212341/picture-diary/skills/recall/SKILL.md

recall

Skill2 starsChanged 17 days agoMITView on GitHub

Look up past diary entries and the rules ledger and apply them to the task at hand. Use before starting work that resembles something that went wrong before, or when the user says "recall", "what did we learn about X", "have we done this before", "과거 일기 찾아줘", "전에도 이랬나".

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

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 129 edited versions we read keep these.

  • 4

    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. Distinctive:

    Search, do not preload. Past diaries are never injected wholesale.

    line 8
  2. Distinctive:

    Search the diaries and the ledger:

    line 11
  3. Distinctive:

    Read only the matching sections of the 1-3 most relevant diaries.

    line 19
  4. Very specific:

    If today's task repeats a known mistake, say so before starting.

    line 21
  5. Distinctive:

    If nothing matches, say "no history on this" and move on.

    line 23

“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

Search, do not preload. Past diaries are never injected wholesale; pull only what matches the task.

  1. Pick 2-4 keywords from the current task (tool names, error text, file or feature names; both languages if the user mixes them).
  2. Search the diaries and the ledger:
    H="${PICTURE_DIARY_HOME:-$HOME/.picture-diary}"
grep -rniE "kw1|kw2" "$H/diary" --include='*.md' | head -40
grep -iE "kw1|kw2" "$H/rules.jsonl"
node "${CLAUDE_PLUGIN_ROOT}/scripts/rules.mjs" status
node "${CLAUDE_PLUGIN_ROOT}/scripts/rules.mjs" report   # when asked whether the rules are working
  3. Read only the matching sections of the 1-3 most relevant diaries.
  4. Answer in this order: (a) rules in force that apply to this task (state graduated, active, or retired), (b) what went wrong last time and on which date, (c) what you will do differently now, as a concrete step.
  5. If today's task repeats a known mistake, say so before starting. If you then make the mistake anyway, record it with rules.mjs hit <tag>.

If nothing matches, say "no history on this" and move on. Do not invent a lesson.

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.

Check your setup, free