hiivmind-corpus-discover

Name: hiivmind-corpus-discover
Availability: InStock
Author: hiivmind

Discover hiivmind documentation corpora and generate structured metadata lists.

1|Updated Dec 7, 2025

Search Tags:#documentation #routing #compatibility #registry #plugins #corpus-discovery #embedded-corpus

Ready to run

npx skills add https://github.com/hiivmind/hiivmind-corpus --skill hiivmind-corpus-discover

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hiivmind-corpus-discover
Source: https://github.com/hiivmind/hiivmind-corpus/tree/main/skills/hiivmind-corpus-discover
Command: npx skills add https://github.com/hiivmind/hiivmind-corpus --skill hiivmind-corpus-discover

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Corpus Discovery skill helps users identify and report all available hiivmind documentation corpora, including registered corpora from the project registry and legacy plugin-based corpora, enabling quick inventory and health checks.

Core Features & Use Cases

Discovery: Locate and list all installed corpora from registry.yaml, embedded corpora, and legacy plugins.
Inventory & Status: Present each corpus with display name, keywords, source, and status to support troubleshooting and planning.
Routing Readiness: Provide metadata to route queries to the appropriate navigate skill for the selected corpus.

Quick Start

Run the discovery flow to enumerate all installed hiivmind corpora and present their statuses.

Frequently Asked Questions about hiivmind-corpus-discover

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

FAQPage Schema

How do I discover all installed documentation corpora in my environment?▼

To discover all installed documentation corpora, run the discovery flow to locate and list registered and legacy plugin-based corpora, generating a structured list with display names, keywords, statuses, and sources.

What is the best way to inventory registered and legacy plugin-based documentation corpora?▼

The best way to inventory documentation corpora is to run a discovery flow that reads registry.yaml and legacy plugin sources, presenting each corpus with its display name, keywords, source, and status for troubleshooting.

How does corpus discovery route generic documentation queries to the correct target?▼

Corpus discovery routes generic documentation queries by generating metadata with keywords and sources, enabling precise routing of queries to the appropriate navigate skill for the selected corpus.

Can I check the health and status of embedded corpora and legacy plugins?▼

Yes, you can check the health and status of embedded corpora and legacy plugins by running the discovery flow, which reports the status of each located corpus from registry.yaml and plugin sources to support troubleshooting.

What metadata do I need to parse from config.yaml and index.md for corpus discovery?▼

For corpus discovery, you need to parse corpus metadata from config.yaml and index.md files to resolve corpus paths and extract display names, keywords, statuses, and sources for structured output.