Skip to content
Back to skills

Index

ASecurity

Context retrieval using the manifest index. Pull only the files relevant to the current task — no full context load. Use at the start of any task to identify which boxes to open. Consult ~/.claude/manifest.json to match task keywords to tags, then read only those files.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 16, 2026
ai-agentspythonbashtestingdebugging

Works with

  • mcp

Security analysis

A100/100

Scanned October 16, 2026

npx -y skills add G-Eskayo/marvin --skill index --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Index?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Index
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/g-eskayo-index/badge)](https://www.skillsdirectory.com/skills/g-eskayo-index)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: index
description: Context retrieval using the manifest index. Pull only the files relevant to the current task — no full context load. Use at the start of any task to identify which boxes to open. Consult ~/.claude/manifest.json to match task keywords to tags, then read only those files.
tags: [intent:retrieve, intent:index, intent:load, type:skill]
calls: [self-improve]
---

# 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:

```bash
~/.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

| Field | Meaning | Examples |
|-------|---------|----------|
| `domain:` (tag) | Subject area | `domain:mcp`, `domain:debugging`, `domain:testing` |
| `intent:` (tag) | What you're doing | `intent:build`, `intent:debug`, `intent:plan` |
| `type:` (tag) | Kind of file | `type:skill`, `type:knowledge`, `type:memory-user` |
| `model-scope` (field) | Model tier restrictions | `sonnet+` (sonnet or better), `haiku,sonnet` (comma list), omitted/`all` (unrestricted) |

## 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
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.