MCP Code Search Tool Selection
Context-Engine-AI/Context-Engine
Rules for choosing Qdrant-Indexer semantic search over grep or file reads when exploring code, debugging or asking where and why questions.
Refreshes or rebuilds the local Lumen semantic code index for the current project, preferring an MCP-driven refresh and reserving the CLI for an explicit clean rebuild.
Install Lumen Index Refresh and Rebuild
$ npx skills add ory/lumen --skill reindex -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ory/lumen reindex --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ory/lumen.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/reindex .claude/skills/reindex && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "reindex" agent skill from https://github.com/ory/lumen/tree/main/skills/reindex into .claude/skills/reindex/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reindex", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ory/lumen/tree/main/skills/reindexType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ory/lumen --skill reindex -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ory/lumen reindex --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ory/lumen.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/reindex .agents/skills/reindex && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "reindex" agent skill from https://github.com/ory/lumen/tree/main/skills/reindex into .agents/skills/reindex/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reindex", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ory/lumen --skill reindex -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ory/lumen reindex --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ory/lumen.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/reindex .cursor/skills/reindex && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "reindex" agent skill from https://github.com/ory/lumen/tree/main/skills/reindex into .cursor/skills/reindex/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reindex", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ory/lumen.git --path skills/reindex--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ory/lumen --skill reindex -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ory/lumen reindex --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ory/lumen.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/reindex .gemini/skills/reindex && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "reindex" agent skill from https://github.com/ory/lumen/tree/main/skills/reindex into .gemini/skills/reindex/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reindex", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ory/lumen reindexInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ory/lumen --skill reindex -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ory/lumen.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/reindex .github/skills/reindex && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "reindex" agent skill from https://github.com/ory/lumen/tree/main/skills/reindex into .github/skills/reindex/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reindex", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ory/lumen --skill reindex -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ory/lumen reindex --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ory/lumen.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/reindex .opencode/skills/reindex && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "reindex" agent skill from https://github.com/ory/lumen/tree/main/skills/reindex into .opencode/skills/reindex/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reindex", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
reindex- GitHub stars
- 307
- Token cost
- ~391 tokens
- SKILL.md length
- 207 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Refreshes or rebuilds the local Lumen semantic code index for the current project, preferring an MCP-driven refresh and reserving the CLI for an explicit clean rebuild.
- Works in 4 steps: Call the Lumen index_status tool for the… → If the user wants the index refreshed or… → If the user explicitly asks for a clean… → …
- Checking whether a project's Lumen index is stale
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Refreshing a project's semantic search index after code changes
What it does
This skill manages the Lumen semantic search index backing a project. It first calls Lumen's `index_status` tool for the current directory to report the current state, then, if you want the index refreshed, calls `semantic_search` with a broad query, which refreshes a stale or missing index automatically as a side effect.
When you explicitly ask for a clean rebuild, it picks between shell commands with different blast radii: `lumen index --force .` reprocesses every file for the current project without touching other worktrees' shared vectors and is preferred; `lumen clean --days 0 && lumen index .` deletes every cached index not held by an active lock before rebuilding, for a full wipe only; `lumen clean` alone removes indexes for projects gone or unused for 30 days, for reclaiming disk space rather than rebuilding. Afterward it reports the new status: vector precision, unique and shared vector counts, deduplication ratio and database size.
When your agent uses it
- Checking whether a project's Lumen index is stale
- Refreshing a project's semantic search index after code changes
- Doing a full clean rebuild of a project's Lumen index
Example prompts
- “Check the Lumen index status for this project and refresh it if stale.”
- “Force a clean rebuild of the Lumen index for the current project only.”
- “Clean up Lumen indexes for projects I have not touched in over a month.”
Requirements
- The Lumen MCP server and CLI
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Call the Lumen index_status tool for the current working directory so you
- If the user wants the index refreshed or seeded, call the Lumen
- If the user explicitly asks for a clean rebuild, explain the options and
- After the refresh or rebuild, report the new index status, including vector
What it can do on your machine
Read from SKILL.md and the folder at commit f60f9ec. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Lumen Index Refresh and Rebuild loads about 391 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 207 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 207 words (~391 tokens).
“Refresh or rebuild the bundled Lumen index for the current project.”
- name
- reindex
Files
Just SKILL.md in skills/reindex of ory/lumen.
Open the folder on GitHubat commit f60f9ec
Compare with similar skills
Lumen Index Refresh and Rebuild next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Lumen Index Refresh and Rebuild this skillory/lumen | 307 | — | ~391 | Automated safety check: Pass | Custom licence | |
| MCP Code Search Tool SelectionContext-Engine-AI/Context-Engine | 402 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Context-Engine Code SearchContext-Engine-AI/Context-Engine | 402 | — | ~14k | Automated safety check: Pass | MIT | |
| Codebase SearchHelweg/open-codebase-index | 216 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Entroly Context Controljuyterman1000/entroly | 474 | — | ~501 | Automated safety check: Pass | Apache-2.0 | |
| Repo Contextnduc99911/repo-context-mcp | 105 | — | ~233 | Automated safety check: Notes | MIT |
Similar skills
Context-Engine Code Search
Context-Engine-AI/Context-Engine
Searches a codebase with hybrid semantic and lexical retrieval plus neural reranking through MCP tools, for finding implementations and grounded answers.
Codebase Search
Helweg/open-codebase-index
Chooses the right retrieval tool for code questions: compact context for unfamiliar repos, direct lookup for known symbols, call graphs for relationships and grep for exhaustive matches.
Entroly Context Control
juyterman1000/entroly
Surgically select, compress, and recover codebase context using Entroly's MCP tools.
Repo Context
nduc99911/repo-context-mcp
Use repo-context-mcp tools to map, search, and pack repository context before large edits or PR review.
Codebase Search Workflow
Helweg/open-codebase-index
Directs an agent to use a local codebase index for repository orientation, definition lookups, call graphs and semantic search before turning to web lookups.
More from ory/lumen
SWE Benchmark Task Adder
ory/lumen
Adds a new task to the bench-swe pipeline from a real GitHub bug-fix issue or pull request, then checks the generated task file and patch.
Lumen Doctor
ory/lumen
Checks the Lumen semantic search setup for the current project: embedding service reachability, index freshness and storage totals, with remediation notes.
Related
Works with
Categories
Questions about Lumen Index Refresh and Rebuild
What does Lumen Index Refresh and Rebuild do?
Refreshes or rebuilds the local Lumen semantic code index for the current project, preferring an MCP-driven refresh and reserving the CLI for an explicit clean rebuild. This skill manages the Lumen semantic search index backing a project. It first calls Lumen's `index_status` tool for the current directory to report the current state, then, if you want the index refreshed, calls `semantic_search` with a broad query, which refreshes a stale or missing index automatically as a side effect.
When should I use Lumen Index Refresh and Rebuild?
Lumen Index Refresh and Rebuild fits situations like: checking whether a project's Lumen index is stale; refreshing a project's semantic search index after code changes; doing a full clean rebuild of a project's Lumen index.
How do I install Lumen Index Refresh and Rebuild in Claude Code?
Run `npx skills add ory/lumen --skill reindex -a claude-code`. Or copy the skill folder (skills/reindex in ory/lumen) into .claude/skills/reindex in your project. Claude Code loads it when a task matches its description.
How do I install Lumen Index Refresh and Rebuild in Codex?
Run `npx skills add ory/lumen --skill reindex -a codex`. Or copy the skill folder (skills/reindex in ory/lumen) into .agents/skills/reindex in your project. Codex loads it when a task matches its description.
Can I use Lumen Index Refresh and Rebuild in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ory/lumen --skill reindex -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/reindex, .gemini/skills/reindex, .github/skills/reindex and .opencode/skills/reindex in your project.
What does Lumen Index Refresh and Rebuild need to run?
SKILL.md names no scripts, command-line tools or credentials: Lumen Index Refresh and Rebuild is instructions for the agent only. Our summary lists: The Lumen MCP server and CLI.
Does Lumen Index Refresh and Rebuild access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Lumen Index Refresh and Rebuild safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Lumen Index Refresh and Rebuild use?
Lumen Index Refresh and Rebuild has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Lumen Index Refresh and Rebuild use?
About 391 tokens (SKILL.md is roughly 1.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Lumen Index Refresh and Rebuild?
Skills that share tags, products or a category with Lumen Index Refresh and Rebuild: MCP Code Search Tool Selection (Context-Engine-AI/Context-Engine, 402 stars), Context-Engine Code Search (Context-Engine-AI/Context-Engine, 402 stars), Codebase Search (Helweg/open-codebase-index, 216 stars) and Entroly Context Control (juyterman1000/entroly, 474 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lumen Index Refresh and Rebuild?
ory (a GitHub organization) maintains it in ory/lumen, which has 307 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on August 11, 2026.
Source: ory/lumen on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.