/index

> Rebuild the full-text search index across all knowledge base files.

170 stars

byMiosa-osa

View on GitHub Installation ↓

Best use case

/index is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

> Rebuild the full-text search index across all knowledge base files.

Teams using /index should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/index/SKILL.md --create-dirs "https://raw.githubusercontent.com/Miosa-osa/canopy/main/library/skills/knowledge/index/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/index/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How /index Compares

Feature / Agent	/index	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

> Rebuild the full-text search index across all knowledge base files.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# /index

> Rebuild the full-text search index across all knowledge base files.

## Usage
```
/index [--full] [--stats]
```

## What It Does
Walks every markdown file in the knowledge base, extracts metadata and content, and rebuilds the SQLite FTS5 search index. Run after major file changes (bulk edits, reorganizations, imports).

## Implementation
Runs: `cd engine && mix optimal.index`

Process:
1. Walk all numbered folders and rhythm/ directory.
2. Parse frontmatter and content from each .md file.
3. Extract entities, topics, and cross-references.
4. Rebuild FTS5 index in SQLite.
5. Report: files indexed, entities found, duration.

With `--stats`: `cd engine && mix optimal.stats` to show index statistics.

## Examples
```bash
# Full reindex
/index

# Reindex and show statistics
/index --stats
```

## Command