agentleFS
Sign inStart free
kaithoughtarchitectkaithoughtarchitect/toppingout/skills/f-archive-search/SKILL.md

f-archive-search

Skill14 starsChanged 20 days agoMITView on GitHub

Search across all ARCHIVED Logbook cards. Use when the user runs /f-archive-search, says "look in the archive", "we knew this before", "search the old cards", or when /f-search came back empty and the knowledge may predate the last rotation. Archived cards only: for live cards use f-search.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Search archived Logbook cards under foreman/logbook/archived/*/entries/.

    line 12
  2. Very specific:

    Never search live foreman/logbook/entries/.

    line 14
  3. Very specific:

    If archived/ has no NNN/ batches (only .gitkeep or empty), say so and point at /f-search.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Topping Out: Logbook archive search

Search archived Logbook cards under foreman/logbook/archived/*/entries/.

Never search live foreman/logbook/entries/. Never query any other knowledge store in place of the files (a repo may keep its own card database or search service; this skill reads only the archived Logbook files). Never invent a card.

If archived/ has no NNN/ batches (only .gitkeep or empty), say so and point at /f-search. Do not print a sample dump as if Archive 001 exists.

Query

Case-insensitive substring over card files. Keep terms simple. Protocol detail: foreman/logbook/ARCHIVE-SYSTEM.md.

How

  1. Glob foreman/logbook/archived/*/entries/**/*.md (do not use Unix ls -d), excluding *TEMPLATE*. Skip missing folders.
  2. Find matches, group by archive number (NNN).
  3. For each hit, read frontmatter: id, type, cluster (cards use cluster:, not section:), title, plus a one-line summary.
  4. One-hop related: grep that card's id in the same archive's logbook_links.md.

Output

Per archive: id, type, cluster, summary, path, related ids if any. Empty query hits: say none found in the batches that exist.

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