From lore
Manages lore indexing and project exclusions for Claude Code and Codex CLI sessions. Guides user through setup, indexing, and opt-out project management.
How this skill is triggered — by the user, by Claude, or both
Slash command
/lore:lore-indexThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Lore uses an **opt-out (blacklist) model**: ALL projects are indexed by default. Users can exclude specific projects they don't want indexed.
Lore uses an opt-out (blacklist) model: ALL projects are indexed by default. Users can exclude specific projects they don't want indexed.
Two source agents are indexed in the same DB:
~/.claude/projects/ (override with CLAUDE_PROJECTS_DIR)~/.codex/sessions/ (override with CODEX_SESSIONS_DIR)Codex sessions are grouped by cwd (read from each file's session_meta line) and surfaced as virtual projects with a codex- dirName prefix. The same project working directory may appear twice in the list — once as a Claude Code project (no prefix) and once as a Codex project (codex- prefix). They are independent rows; excluding one does not affect the other.
If the user has never used lore indexing before, or asks to index without context, walk them through:
status to see if anything is indexed, then manage_projects(action: "list") to see available projects.index())? Exclude certain projects first?Do not skip the explanation step. The user needs to understand what's happening.
| User intent | Tool call | Existing data |
|---|---|---|
| Index everything (default) | index() -- incremental index for all non-excluded projects | Preserved |
| Index a specific project | index(project: "/full/path/to/project") -- indexes that project (even if excluded) | Preserved |
| Start fresh | index(mode: "rebuild") -- deletes ALL indexed data and re-indexes from scratch | Deleted |
| Stop running index | index(mode: "cancel") | -- |
Important: Always use full project paths, not fuzzy names. Never summarize or drop rows from tool results when presenting to the user.
| User intent | Tool call |
|---|---|
| See available projects | manage_projects(action: "list") |
| Stop indexing a project | manage_projects(action: "exclude", projects: ["/full/path"]) -- adds to blacklist + cleans DB data |
| Undo an exclusion | manage_projects(action: "include", projects: ["/full/path"]) -- removes from blacklist, next index picks it up |
When the user asks to exclude or include, confirm which project they mean. If ambiguous, show the list first.
After starting indexing, check progress with status. It shows:
Indexing runs in the background -- the user can search while it's in progress.
These happen without user intervention:
Rebuild deletes all indexed data and re-indexes from scratch. Suggest it only when:
Always explain that rebuild can take several minutes for large projects.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub hyunjae-labs/clauder --plugin lore