agentleFS
Sign inStart free
modeled-information-formatmodeled-information-format/mnemonic/skills/qmd-reindex/SKILL.md

qmd-reindex

Skill23 starsChanged 10 months agoMITView on GitHub

Re-index mnemonic memories for qmd semantic search. Run after capturing new memories or bulk imports.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After bulk memory imports

    line 38
  2. Distinctive:

    After editing memory files directly

    line 39

≈ “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

QMD Re-index Skill

Re-index mnemonic memories for qmd search.

Usage

qmd update && qmd embed
  • qmd update — rebuilds the BM25 full-text index
  • qmd embed — regenerates vector embeddings for semantic search

Options

# Index only (skip embeddings — faster)
qmd update

# Specific collection only
qmd update -c mnemonic-zircote && qmd embed -c mnemonic-zircote

# Check status after
qmd status

When to Re-index

  • After /mnemonic:capture sessions
  • After bulk memory imports
  • After editing memory files directly
  • Periodically if memories are added by hooks

Indexing is not automatic. Searches will miss memories added since the last index.

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