hiivmind-corpus-build

Build and index a multi-source documentation corpus into index.yaml and index.md.

1|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/hiivmind/hiivmind-corpus --skill hiivmind-corpus-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hiivmind-corpus-build
Source: https://github.com/hiivmind/hiivmind-corpus/tree/main/skills/hiivmind-corpus-build
Command: npx skills add https://github.com/hiivmind/hiivmind-corpus --skill hiivmind-corpus-build

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Building and maintaining a coherent, searchable index for a multi-source documentation corpus is complex and error-prone without automation. This skill orchestrates corpus initialization, source prep, scan, segmentation choices, user preferences, index generation, optional embeddings, and graph relationships to produce a production-ready index (index.yaml) and a rendered index (index.md) with consistent metadata across sources.

Core Features & Use Cases

  • Orchestrates end-to-end corpus indexing from zero or placeholder indices to a structured index.yaml and rendered index.md.
  • Supports multi-source, tiered or single-file indexing, with optional graph relationships and embeddings.
  • Ideal for teams who need repeatable, auditable corpus builds for documentation, API references, and learning resources.

Quick Start

Start the build by running this skill in the context of your corpus to generate index files and populate metadata.

Frequently Asked Questions about hiivmind-corpus-build

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

FAQPage Schema
How do I automate building a documentation index from multiple sources?

Automating documentation index builds from multiple sources requires orchestrating source preparation, scanning, segmentation, and index generation to produce a structured index.yaml and rendered index.md with consistent metadata across all sources.

What is the best way to create a searchable documentation corpus with graph relationships and embeddings?

Creating a searchable documentation corpus with graph relationships and embeddings involves configuring corpus initialization, applying optional embeddings, and generating graph data to produce a production-ready index with semantic search capabilities.

Can I use configurable segmentation for multi-source documentation corpora?

Configurable segmentation for multi-source documentation corpora is supported, allowing tiered or single-file indexing with user preferences applied during the segmentation phase to ensure consistent metadata across sources.

How do I generate index.yaml and index.md files for API references and learning resources?

Generating index.yaml and index.md files for API references and learning resources requires running an end-to-end corpus indexing process that handles configuration, scanning, segmentation, and finalization to output both structured and rendered index formats.

Does corpus indexing work with repeatable, auditable builds for documentation?

Corpus indexing supports repeatable, auditable builds for documentation by orchestrating the full pipeline from initial config through finalization, ensuring consistent metadata and producing production-ready index files across multiple sources.

What are the phases for building a documentation corpus index from zero?

Building a documentation corpus index from zero involves phases for config, preparation, scanning, segmentation, user preferences, index generation, graph data, embeddings, and finalization to produce a structured and rendered index.