hiivmind-corpus-register

Register documentation corpora from GitHub, local paths, or URLs into registry.yaml.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables you to register a documentation corpus with the current project by updating the corpus registry file (.hiivmind/corpus/registry.yaml) with source information so teams can discover and access shared documents.

Core Features & Use Cases

  • Register a corpus from GitHub, local path, or a URL and create or update a registry entry.
  • Validate required corpus metadata (config.yaml and index.md) and capture keywords for routing.
  • Manage cache and access details to keep corpora fresh and accessible across projects.

Quick Start

Provide a corpus source reference to register, then the system will create or update the registry.yaml accordingly.

Frequently Asked Questions about hiivmind-corpus-register

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

FAQPage Schema
How do I register a local documentation corpus into a project registry?

To register a local documentation corpus, you provide the local path to the skill, which validates required metadata files like config.yaml and index.md, then creates or updates the registry.yaml file with the corpus source information and keywords.

Can I register a corpus from a GitHub repository into my project?

Yes, you can register a corpus from a GitHub repository by providing its source reference. The skill parses the GitHub source, validates necessary corpus files, and updates the project's registry.yaml with the source type and metadata.

What files are required to validate a corpus during registration?

Validating a corpus during registration requires specific metadata files, specifically config.yaml and index.md. The registration process checks for these required files before successfully storing the corpus metadata in the registry.

How does corpus registration handle caching and metadata updates?

Corpus registration manages caching and metadata updates by optionally adjusting cache settings when creating or updating a registry entry. It stores the validated metadata in registry.yaml to keep the corpus fresh and accessible across projects.

What is the purpose of the registry.yaml file in corpus management?

The registry.yaml file serves as the central registry for managing corpus sources within a project. It stores validated metadata, source types, IDs, and keywords, enabling teams to discover and access shared documents.

Does corpus registration work with URL sources besides local paths and GitHub?

Yes, corpus registration supports adding a corpus reference from a URL, alongside GitHub and local paths. The skill parses the URL source, validates the required files, and stores the information in the project's registry.yaml.