agentleFS
iagocavalcanteiagocavalcante/claude-turbo-search/skills/turbo-index/SKILL.md

turbo-index

Skill16 starsChanged 20 days agoMITView on GitHub

Set up project-scoped document search and persistent memory in Claude Code or Codex. Refresh after documentation changes.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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. Very specific:

    Check dependencies with bash "$PLUGIN_DIR/scripts/install-deps.sh" --check-only.

    line 10
  2. Distinctive:

    Verify with a real project term:

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Turbo Index

Resolve PLUGIN_DIR to the absolute directory two levels above this skill file, resolving symlinks. Set it in each shell invocation; keep the working directory in the target repository.

  1. Check dependencies with bash "$PLUGIN_DIR/scripts/install-deps.sh" --check-only. Install missing dependencies using the same script without --check-only when authorized.
  2. Build the memory executable and initialize the current project's memory:

    bash "$PLUGIN_DIR/scripts/setup-memory.sh"
  3. For a standalone skills installation, register MCP for the client being used:

    bash "$PLUGIN_DIR/scripts/setup-mcp.sh" --client codex
    # Use --client claude or --client both as appropriate.

    Preserve existing servers. If qmd is already registered, inspect it before changing it. The project adapter must run scripts/qmd-mcp.sh, not an old global qmd mcp command. See the README migration instructions.

  4. Index current Markdown documentation:

    python3 "$PLUGIN_DIR/scripts/turbo.py" index

    This uses a dedicated QMD index/collection for this checkout, snapshots allowed Markdown files, respects ignore files and excludes hidden paths, symlinks and sensitive filenames. It does not embed by default. Use index --embed when semantic search is wanted; model downloads can be large. Embedding failure leaves keyword search available.

  5. Verify with a real project term:

    python3 "$PLUGIN_DIR/scripts/turbo.py" search "authentication"
    python3 "$PLUGIN_DIR/scripts/turbo.py" doctor

Report what actually succeeded, missing dependencies and stale indexes. Do not claim measured token savings without measurements. Index refresh is explicit and never runs in a prompt hook.

Optional: install hooks with bash "$PLUGIN_DIR/scripts/setup-hooks.sh" --client codex --rag --memory (or claude). For Claude only, setup-file-suggestion.sh adds file suggestions. Cartographer is optional; use it only if available and useful.

The --memory option installs activity capture plus local PreCompact/SessionEnd checkpoints. These save bounded file/tool observations without reading transcripts or inferring unfinished work. Re-run hook setup after upgrading to register these handlers; hooks never initialize a missing database. Use /remember for durable conclusions and a structured handoff.

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.