Basemind Code Context
Goldziher/basemind
Answers structural questions about a repository, such as where a symbol is defined, what calls it and what changed recently, through the basemind MCP server.
Checks the Lumen semantic search setup for the current project: embedding service reachability, index freshness and storage totals, with remediation notes.
Install Lumen Doctor
$ npx skills add ory/lumen --skill doctor -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ory/lumen doctor --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/doctor .claude/skills/doctor && 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 "doctor" agent skill from https://github.com/ory/lumen/tree/main/skills/doctor into .claude/skills/doctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doctor", 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/doctorType 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 doctor -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ory/lumen doctor --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/doctor .agents/skills/doctor && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "doctor" agent skill from https://github.com/ory/lumen/tree/main/skills/doctor into .agents/skills/doctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doctor", 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 doctor -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ory/lumen doctor --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/doctor .cursor/skills/doctor && 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 "doctor" agent skill from https://github.com/ory/lumen/tree/main/skills/doctor into .cursor/skills/doctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doctor", 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/doctor--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 doctor -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ory/lumen doctor --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/doctor .gemini/skills/doctor && 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 "doctor" agent skill from https://github.com/ory/lumen/tree/main/skills/doctor into .gemini/skills/doctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doctor", 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 doctorInstalls 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 doctor -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/doctor .github/skills/doctor && 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 "doctor" agent skill from https://github.com/ory/lumen/tree/main/skills/doctor into .github/skills/doctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doctor", 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 doctor -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 doctor --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/doctor .opencode/skills/doctor && 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 "doctor" agent skill from https://github.com/ory/lumen/tree/main/skills/doctor into .opencode/skills/doctor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doctor", 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
doctor- GitHub stars
- 307
- Token cost
- ~339 tokens
- SKILL.md length
- 170 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Checks the Lumen semantic search setup for the current project: embedding service reachability, index freshness and storage totals, with remediation notes.
- Works in 6 steps: Call the Lumen health_check tool to… → Call the Lumen index_status tool with… → Report a concise summary → …
- Semantic search results look empty or stale
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Verifying the embedding backend is reachable after installing the plugin
What it does
Two Lumen tools do the work. The health_check tool confirms that the embedding service can be reached, and index_status, pointed at the current working directory, reports whether the project's index is fresh or stale. The agent then summarizes the embedding service status, backend, host and model; index totals such as files, chunks and last indexed time; storage totals including unique vectors, shared references, vector precision, database size and reclaimable bytes; and any MCP or plugin problem that blocks the tools.
Guidance for edge cases is built in. With no index yet, the agent explains that the first semantic_search call seeds it, and for eager indexing it suggests running lumen index in the repository root. Storage figures are read as collection-wide values shared by compatible Git worktrees, while file, chunk and freshness figures belong to the project, and a high deduplication ratio is expected rather than a fault.
When your agent uses it
- Semantic search results look empty or stale
- Verifying the embedding backend is reachable after installing the plugin
- Checking how large the Lumen index is and how much space is reclaimable
Example prompts
- “Run the Lumen doctor and tell me whether the index for this project is fresh.”
- “Semantic search returns nothing, so check that the embedding service is reachable.”
- “Report how much disk space the Lumen index uses for this project and how much is reclaimable.”
Requirements
- The Lumen plugin or MCP server installed
- A reachable embedding backend for Lumen
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Call the Lumen health_check tool to verify the embedding service is
- Call the Lumen index_status tool with path or cwd set to the current
- Report a concise summary
- If no index exists yet, explain that the Lumen semantic_search tool seeds
- If the user wants eager indexing instead of waiting for the next search,
- Interpret storage totals as collection-wide values shared by compatible Git
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 Doctor loads about 339 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 170 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 170 words (~339 tokens).
“Run a health check on the bundled Lumen semantic search setup for the current project.”
- name
- doctor
Files
Just SKILL.md in skills/doctor of ory/lumen.
Open the folder on GitHubat commit f60f9ec
Compare with similar skills
Lumen Doctor 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 Doctor this skillory/lumen | 307 | — | ~339 | Automated safety check: Pass | Custom licence | |
| Basemind Code ContextGoldziher/basemind | 108 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Codebase Managementgiancarloerra/SocratiCode | 3.3k | 1 repos | ~1.8k | Automated safety check: Pass | AGPL-3.0 | |
| Agent Deckasheshgoplani/agent-deck | 1k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Foremergenaw103/foremerge | 538 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Puppetmaster Agent Orchestrationprofessorpalmer/Puppetmaster | 467 | — | ~3.2k | Automated safety check: Pass | MIT |
Similar skills
Codebase Management
giancarloerra/SocratiCode
Set up, index, and manage SocratiCode codebase indexing. An agent skill from giancarloerra/SocratiCode.
Agent Deck
asheshgoplani/agent-deck
agent-deck, the terminal session manager for AI coding agents.
Foremerge
naw103/foremerge
Coordinate parallel coding agents with Foremerge's local Git-compatible CLI and MCP server.
Puppetmaster Agent Orchestration
professorpalmer/Puppetmaster
Operates and supervises Puppetmaster, a multi-agent orchestrator, through its MCP tools or CLI, picking the right verb for edits, reviews, audits and long-running jobs.
Agent Recall
Goldentrii/AgentRecall-X
Persistent compounding memory for AI agents. An agent skill from Goldentrii/AgentRecall-X.
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 Index Refresh and Rebuild
ory/lumen
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.
Related
Works with
Categories
Questions about Lumen Doctor
What does Lumen Doctor do?
Checks the Lumen semantic search setup for the current project: embedding service reachability, index freshness and storage totals, with remediation notes. Two Lumen tools do the work. The health_check tool confirms that the embedding service can be reached, and index_status, pointed at the current working directory, reports whether the project's index is fresh or stale.
When should I use Lumen Doctor?
Lumen Doctor fits situations like: semantic search results look empty or stale; verifying the embedding backend is reachable after installing the plugin; checking how large the Lumen index is and how much space is reclaimable.
How do I install Lumen Doctor in Claude Code?
Run `npx skills add ory/lumen --skill doctor -a claude-code`. Or copy the skill folder (skills/doctor in ory/lumen) into .claude/skills/doctor in your project. Claude Code loads it when a task matches its description.
How do I install Lumen Doctor in Codex?
Run `npx skills add ory/lumen --skill doctor -a codex`. Or copy the skill folder (skills/doctor in ory/lumen) into .agents/skills/doctor in your project. Codex loads it when a task matches its description.
Can I use Lumen Doctor 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 doctor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/doctor, .gemini/skills/doctor, .github/skills/doctor and .opencode/skills/doctor in your project.
What does Lumen Doctor need to run?
SKILL.md names no scripts, command-line tools or credentials: Lumen Doctor is instructions for the agent only. Our summary lists: The Lumen plugin or MCP server installed; A reachable embedding backend for Lumen.
Does Lumen Doctor 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 Doctor 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 Doctor use?
Lumen Doctor 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 Doctor use?
About 339 tokens (SKILL.md is roughly 1.4k 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 Doctor?
Skills that share tags, products or a category with Lumen Doctor: Basemind Code Context (Goldziher/basemind, 108 stars), Codebase Management (giancarloerra/SocratiCode, 3.3k stars), Agent Deck (asheshgoplani/agent-deck, 1k stars) and Foremerge (naw103/foremerge, 538 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lumen Doctor?
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.