agentleFS
anneheartrecordanneheartrecord/charles-skill/skills/spool/SKILL.md

spool

Skill3 starsChanged 3 months agoMITView on GitHub

Search your local Claude Code and Codex CLI session history

  • Installs packages

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search your thinking with spool — a local search engine over your Claude Code and Codex CLI sessions.

    line 7
  2. Distinctive:

    If the command is not found, tell the user:

    line 17
  3. Very specific:

    Ask: "Want to see the full conversation for any of these?

    line 50
  4. Distinctive:

    If the user says yes (or specifies a number/UUID), run:

    line 52
  5. Very specific:

    Add --source claude or --source codex to filter by source

    line 62
  6. Very specific:

    Add --since 7d to limit to the last 7 days

    line 63
  7. Very specific:

    Use quotes for exact phrases: /spool "read replicas"

    line 64
  8. Very specific:

    Run spool sync first if results seem stale

    line 65

“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

Search your thinking with spool — a local search engine over your Claude Code and Codex CLI sessions.

Steps

  1. Check if spool is installed
which spool

If the command is not found, tell the user:

spool CLI is not installed. Run: npm install -g @spool/cli then spool sync to index your sessions. Stop here.

  1. Run the search
spool search "$ARGS" --json --limit 5

where $ARGS is everything the user passed to /spool.

  1. Present the results

For each result in the JSON array, show:

  • Session title and date (startedAt)
  • Source (claude or codex) and project path
  • The snippet with highlighted terms (strip <mark> / </mark> tags for plain display)
  • A note of the session UUID

Example format:

1. [claude] /code/myproject — 2026-03-20
   "…evaluated the database sharding tradeoffs and reached a decision…"
   UUID: abc123

2. [codex] /code/api — 2026-03-18
   "…the race condition was caused by a shared map write without a mutex…"
   UUID: def456
  1. Offer to load a full session

Ask: "Want to see the full conversation for any of these? I can load it with spool show <uuid>."

If the user says yes (or specifies a number/UUID), run:

spool show <uuid>

Include the output as context in your next reply.

Tips

  • Add --source claude or --source codex to filter by source
  • Add --since 7d to limit to the last 7 days
  • Use quotes for exact phrases: /spool "read replicas"
  • Run spool sync first if results seem stale

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.