agentleFS
Sign inStart free
stackqlstackql/stackql-skills/skills/read-memories/SKILL.md

read-memories

Skill0 starsChanged 8 months agoMITView on GitHub

Search past Claude Code session logs to recover your own context. Invoke this proactively when you need to recall past decisions, patterns, or unresolved work - either across all projects or scoped to the current one.

3 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 3

    1. duckdb/duckdb-skills★ 59821% same
    2. opengeos/geoai-skills★ 3115% same
    3. carlopi/duckdb-claude-skills★ 273% same

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository10 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. 2 are common, 3 are distinctive, and 1 is very specific to this project.

  • 2

    Common

    Most of the 3 edited versions we read keep these.

  • 3

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

    Use this to recover your own context from past sessions.

    line 11
  2. Very specific:

    Use $CURRENT_PROJECT if $1 is --here, otherwise use $ALL_PROJECTS.

    line 25
  3. Distinctive:

    Use grep to search through the JSONL session logs:

    line 29
  4. Distinctive:

    If Step 2 returns more than 40 matches or the output is very large, narrow down:

    line 45
  5. Distinctive:

    Add more specific search terms

    line 47
  6. Common:

    Use this to inform your current response.

    line 59

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

Use this to recover your own context from past sessions. Do NOT narrate the process to the user - silently run the query, absorb the results, and continue with enriched context.

$0 is the keyword to search for. Pass --here as a second argument ($1) to scope the search to the current project only.

Step 1 - Set the search path

ALL_PROJECTS="$HOME/.claude/projects/*/*.jsonl"
CURRENT_PROJECT="$HOME/.claude/projects/$(echo "$PWD" | sed 's|[/_]|-|g')/*.jsonl"

Use $CURRENT_PROJECT if $1 is --here, otherwise use $ALL_PROJECTS.

Step 2 - Query

Use grep to search through the JSONL session logs:

grep -r -l "<KEYWORD>" <SEARCH_PATH> 2>/dev/null

Then for each matching file, extract relevant context:

grep -i "<KEYWORD>" <FILE> | head -40

Replace <SEARCH_PATH> and <KEYWORD> with the resolved values before running.

Step 3 - Handle large result sets

If Step 2 returns more than 40 matches or the output is very large, narrow down:

  • Add more specific search terms
  • Scope to the current project with --here
  • Filter by date if relevant

Step 4 - Internalize

From the results, extract:

  • Decisions made and their rationale
  • Patterns and conventions established
  • Unresolved items or open TODOs
  • Any corrections the user made to your prior behavior

Use this to inform your current response. Do not repeat back the raw logs to the user.

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