hiivmind-corpus-status

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

Inspect corpus registries and YAML configs to report index freshness and caching state.

1|Updated Dec 7, 2025

Search Tags:#registry #status #update #diagnose #health #index #corpus

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quickly determine the health and freshness of their registered corpora by aggregating status from the registry, per-corpus configuration, and index data.

Core Features & Use Cases

Load the corpus registry from .hiivmind/corpus/registry.yaml and enumerate corpora.
Validate each corpus configuration (config.yaml) for required fields and source definitions.
Verify index existence and last updated timestamps to surface stale entries.
Compare source freshness against upstream commits to highlight out-of-date content.
Generate a concise, actionable status report suitable for quick triage and maintenance.

Quick Start

Ask /hiivmind-corpus status to view the health snapshot for all registered corpora.

Frequently Asked Questions about hiivmind-corpus-status

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

FAQPage Schema

How do I check corpus health and index freshness for multiple registered corpora?▼

To check corpus health and index freshness, load the corpus registry and parse per-corpus config.yaml files to assess index existence, source freshness, and caching state, generating a concise status overview for quick triage.

What is a corpus registry and how does it track data freshness?▼

A corpus registry tracks data freshness by recording configurations in registry.yaml and per-corpus config.yaml files, verifying index timestamps and comparing source freshness against upstream commits to highlight out-of-date content.

How do I diagnose stale indices in a multi-corpus project?▼

Diagnose stale indices by inspecting the corpus registry and per-corpus config.yaml to verify index existence and last updated timestamps, comparing source freshness against upstream commits to surface stale entries requiring maintenance.

Can I validate corpus configuration files for required fields and source definitions?▼

Yes, you can validate corpus configuration by parsing per-corpus config.yaml files, checking for required fields and source definitions during the registry loading process to ensure configurations are complete and correctly structured.

Does this corpus status check report on upstream source changes?▼

Yes, the corpus status check compares source freshness against upstream commits to highlight out-of-date content, coordinating registry loading and upstream change assessment to produce an actionable status report.

When should I run a corpus health snapshot for my registered data sources?▼

Run a corpus health snapshot during multi-corpus project maintenance to diagnose index existence, source freshness, and caching state, providing fast triage to determine if registered corpora are out-of-date.