index

Index project source files and documentation into a vector store for semantic search.

161|21|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/softspark/ai-toolkit --skill index-softspark
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: index
Source: https://github.com/softspark/ai-toolkit/tree/main/app/skills/index
Command: npx skills add https://github.com/softspark/ai-toolkit --skill index-softspark

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping a codebase searchable through semantic search requires an up‑to‑date vector index; manual updates are error‑prone and slow.

Core Features & Use Cases

  • Incremental indexing that detects file changes, additions, or deletions.
  • Full rebuild option for complete re‑indexing.
  • Docker‑compatible commands for containerized environments.
  • Validation of document frontmatter before indexing.

Quick Start

Use the /index --full command to perform a complete re‑index of the knowledge base.

Frequently Asked Questions about index

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I index a codebase for semantic search?

To index a codebase for semantic search, you process project source files and documentation into a vector store. This requires a configured vector database like Qdrant and properly formatted frontmatter in each knowledge base document.

How does incremental indexing work for codebase documentation?

Incremental indexing detects file changes, additions, or deletions within your codebase. It updates the vector store with only the modified documents, avoiding the need to process the entire project repeatedly.

Do I need a vector database to perform semantic search on my codebase?

Yes, you need a configured vector database such as Qdrant to store and query the generated embeddings. The indexing process relies on this vector store to enable instant semantic search.

Can I run a full rebuild of my codebase index in a Docker environment?

Yes, you can run a full rebuild of your codebase index using Docker-compatible commands. Executing a complete re-index in a containerized environment ensures a clean and consistent vector store state.

What is the best way to update a vector index after modifying source files?

The best way to update a vector index after modifying source files is through incremental indexing, which automatically detects the changes. Alternatively, use a full rebuild command to re-index the entire knowledge base from scratch.

Why does my codebase indexing fail when processing documentation?

Codebase indexing fails when knowledge base documents lack properly formatted frontmatter. The indexing process validates document frontmatter before adding the source files to the vector store.