g-eskayo/marvin/index

Index — Pull the Right Boxes

Pull exactly the boxes the task needs. Nothing else.

Primary: hybrid retrieval engine

retrieve.py is the real engine — semantic (ChromaDB + Ollama) + BM25 keyword, merged via RRF, with intent-aware thresholds. Use it first.

MUST run via the venv interpreter — bare python3 lacks the deps and silently degrades to tag matching:

~/.agents/venv/bin/python ~/.agents/skills/self-improve/scripts/retrieve.py "<task description>" --intent <intent> --model <your-tier>

--intent tunes precision/recall: debug/fix/diagnose (precise), create/ideate/brainstorm (recall), plan/research/tdd (mid). Omit if unsure.

--model (optional) filters results by which Claude model can run them. Pass your current tier (haiku, sonnet, or opus) — you'll find it in your system context. Add --json for structured output.

Then load the returned paths. Check each loaded skill's calls: and load those too if the task needs them.

Fallback: manual manifest matching

If the engine prints INFO: ... tag fallback or returns nothing, match by hand:

1. Read the request — extract 2–4 keywords describing the task
2. Read `~/.claude/manifest.json` — scan the index[] array
3. Collect entries whose tags intersect the task keywords
4. Skip any entries whose model-scope excludes your current tier (check your system context for which model you're running)
5. Load those files — read each matched path
6. Check `calls` — if a loaded skill declares calls: [x, y], load those too if the task needs them
7. Proceed with only what's relevant

~/.claude/manifest.json is the unified index for all skills AND knowledge files. Each entry has name, path, tags[], optionally model-scope, and optionally calls[]. Tags use namespace:value — domain:, intent:, type:.

Tag Namespaces & Fields

Examples

"There's a bug in the auth middleware" Keywords: debug, fix → match intent:debug, intent:fix Load: diagnose skill Also check: domain:auth entries → reference_mcp.md if MCP-related

"Let's TDD the payment feature" Keywords: tdd, test, build → match domain:testing, intent:tdd, intent:build Load: tdd skill (which calls: [diagnose] if needed)

"Help me build an MCP server" Keywords: build, mcp → match domain:mcp, intent:build Load: reference_mcp.md (knowledge) + research/build skills

Manifest Structure

always          — loaded every session (CLAUDE.md, lexicon.md)
on_session_start — checked at session start (handoffs, suggestions)
index[]         — flat array of all tagged entries:
  name          — identifier
  path          — file to read (~ = home)
  tags          — namespaced tag array
  calls         — (optional) other skills this one may invoke

Keeping the Manifest Current

Manifest is auto-generated from frontmatter. Do not edit it by hand.

When creating a new skill or memory file:

1. Add tags: [namespace:value, ...] to its frontmatter
2. Add calls: [skill-name, ...] if it depends on other skills
3. The PostToolUse hook runs rebuild-manifest.py automatically

To rebuild manually (use the venv interpreter — same dep requirement as retrieve.py):

~/.agents/venv/bin/python ~/.agents/skills/self-improve/scripts/rebuild-manifest.py