hub-indexer

Parse frontmatter and build domain indexes for hub documents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mattfuster/aisef-setup --skill hub-indexer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hub-indexer
Source: https://github.com/mattfuster/aisef-setup/tree/main/.claude/skills/hub-indexer
Command: npx skills add https://github.com/mattfuster/aisef-setup --skill hub-indexer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The hub-indexer keeps the AISEF hub navigable by creating and maintaining a master index of every document. It reads frontmatter, normalizes domain assignments, and surfaces cross-reference relationships so Claude and humans can find, relate, and trust hub content quickly.

Core Features & Use Cases

  • Build and refresh domain-specific indexes from 01-requirements, 02-blueprints, 03-work-orders, 04-sprints, 05-decisions, 06-questions, 07-issues, and 08-artifacts.
  • Generate a root hub index and a compact hub map for efficient memory usage and fast lookups.
  • Backfill missing frontmatter and validate cross-references to keep the hub's metadata accurate over time.
  • Use cases: reindex the hub on demand, backfill frontmatter for new or migrated docs, query the hub for all items related to a topic, or refresh the team dashboard with current assignments.

Quick Start

Ask the hub to reindex the hub to refresh all indexes.

Frequently Asked Questions about hub-indexer

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

FAQPage Schema
How do I build a searchable index from frontmatter across a knowledge management repository?

To build a searchable knowledge management index, the hub-indexer parses frontmatter from hub documents to create domain-specific indexes, enforcing taxonomy and cross-reference relationships for instant navigation.

What is the best way to backfill missing frontmatter metadata for migrated documents?

Backfilling missing frontmatter is handled during the hub indexing process, which normalizes domain assignments and validates cross-references to keep hub metadata accurate over time.

Can I generate domain indexes for specific document categories like requirements and blueprints?

Yes, domain indexes can be generated for specific categories including requirements, blueprints, work orders, sprints, decisions, questions, issues, and artifacts.

How do I maintain cross-reference relationships between documents in a knowledge hub?

Maintaining cross-reference relationships is achieved by parsing frontmatter and validating links during indexing, ensuring documents remain connected and navigable.

Does hub-indexer work without external dependencies to refresh a hub dashboard?

Yes, the hub-indexer operates with no external dependencies, refreshing the team dashboard with current assignments by generating a root index and a compact hub map.