This skill should be used when the user asks "what corpora do I have installed?", "list my documentation corpora", "find installed corpus plugins", "what hiivmind-corpus plugins are available?", "check the docs", "search the documentation", "what do the docs say", "look up in corpus", or needs to discover installed documentation corpus skills. Also use when a generic documentation query doesn't specify which corpus to search.
Find and report all available documentation corpora, including:
.hiivmind/corpus/registry.yamlWhen triggered by a generic query like "check the docs" or "what do the docs say about X":
"I found these documentation corpora:
Which would you like me to search? Or rephrase your question with a specific domain."
Check .hiivmind/corpus/registry.yaml for registered corpora:
Read: .hiivmind/corpus/registry.yaml
Registry corpora are data-only repositories accessed via GitHub or local paths.
See: lib/corpus/patterns/registry-loading.md for registry schema and loading.
Check .hiivmind/corpus/config.yaml in the current repo:
Read: .hiivmind/corpus/config.yaml
If it exists and contains corpus.name, this is an embedded corpus. Extract corpus.name, corpus.display_name, corpus.keywords directly.
Name derivation: use corpus.name field (required for embedded corpora since the directory is always corpus/).
Scan these locations for plugin-based corpora:
| Type | Location Pattern | Structure |
|---|---|---|
| User-level | ~/.claude/skills/hiivmind-corpus-*/ | Skill with data/config.yaml |
| Repo-local | .claude-plugin/skills/hiivmind-corpus-*/ | Skill in current repo |
| Marketplace single | ~/.claude/plugins/marketplaces/hiivmind-corpus-*/ | Standalone corpus plugin |
| Marketplace multi | ~/.claude/plugins/marketplaces/*/hiivmind-corpus-*/ | Corpus inside a marketplace |
First, check if the project has a corpus registry:
Read: .hiivmind/corpus/registry.yaml
If registry exists, extract registered corpora:
# Registry structure