
file-indexer
Indexes files by generating AI summaries and maintaining a lightweight catalog alongside your files. Supports Inbox-based filing workflows.
- version
- 1.0.0
Install
/plugin install file-indexer@effective-claudeRun it inside Claude Code after adding the marketplace with /plugin marketplace add zjor/effective-claude.
Contents
Discovered from sourceCommands 1
Index a file: read its content, generate a summary, and create index artifacts in the file's folder.
Arguments
$ARGUMENTS may contain:
- nothing — ask the user which file to index
<filepath>— index the specified file in place (unless it's in an Inbox folder)<filepath> <destination>— move the file to destination, then index it there
Step 1: Resolve the target file
If no filepath was provided in $ARGUMENTS, ask the user:
Which file would you like to index?
Step 2: Check for Inbox
Check whether any component of the file's current path is a folder named inbox (case-insensitive).
- If yes (Inbox file): ask the user for the destination folder (unless already provided as the second argument).
- Move the file to the destination folder before proceeding.
- All further steps operate on the file at its new location.
- If no: proceed with the file in its current location. No moving needed.
Step 3: Read and understand the file
Read the file content. Identify:
- What kind of document it is (report, article, code, notes, invoice, etc.)
- Its main topic and key points
- Any important metadata (date, author, subject, etc.)
Step 4: Create .index/ directory if needed
In the folder where the file now lives, check for a .index/ subdirectory.
If it does not exist, create it.
Step 5: Write the summary to .index/<filename>.md
Create (or overwrite) .index/<original-filename>.md with a structured summary:
# <Original Filename>
**Type:** <document type>
**Date indexed:** <today's date>
## Summary
<3–6 sentence summary capturing the main content, purpose, and key points>
## Key Points
- <bullet 1>
- <bullet 2>
- ...
Keep it informative but concise — this is a reference document.
Step 6: Update CLAUDE.md in the file's folder
Check if CLAUDE.md exists in the file's folder.
- If not, create it with a header:
# Folder Index
Append the following entry to CLAUDE.md (do not duplicate if the file was already indexed):
## <original-filename>
<One to two sentence description — shorter than the summary. Captures what the file is and why it matters.>
If an entry for this filename already exists in CLAUDE.md, replace it with the updated snippet.
Step 7: Confirm to the user
Report what was done:
- File location (original → new, if moved)
- Path to the summary file created in
.index/ - Whether
CLAUDE.mdwas created or updated
Agents 1
file-indexer
A Claude Code plugin that indexes files by generating AI summaries and keeping a lightweight catalog alongside your files.
What it does
When you run /index-file, Claude will:
- Read and understand the file
- Create a
.index/<filename>.mdwith a structured summary - Append a short snippet to
CLAUDE.mdin the same folder
If the file lives in an Inbox folder (case-insensitive), Claude will ask where to move it before indexing.
Installation
Copy .claude/commands/index-file.md into your project's .claude/commands/ folder, or place it in ~/.claude/commands/ to make it available globally.
Usage
/index-file # Claude asks which file to index
/index-file path/to/file.pdf # Index a specific file in place
/index-file Inbox/report.pdf ~/Docs/ # Move from Inbox to destination, then index
Artifacts created
Given a file at ~/Docs/report.pdf:
~/Docs/
report.pdf
CLAUDE.md ← short snippet appended here
.index/
report.pdf.md ← full summary
.index/report.pdf.md (summary)
# report.pdf
**Type:** Research report
**Date indexed:** 2026-02-20
## Summary
...
## Key Points
- ...
CLAUDE.md entry
## report.pdf
A Q4 2025 market research report covering competitor analysis and pricing trends.
Sponsors
Details
- Marketplace
- zjor/effective-claude
- Source
- file-indexer
- Author
- zjor
- Category
- Community
- Keywords
- indexing, files, summary, productivity, inbox, catalog