index

Validates Markdown frontmatter and regenerates INDEX.md files for documentation directories.

Updated May 3, 2026
One-click install
npx skills add https://github.com/Claudfather/clauDNA --skill index-claudfather
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: index
Source: https://github.com/Claudfather/clauDNA/tree/main/skills/index
Command: npx skills add https://github.com/Claudfather/clauDNA --skill index-claudfather

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shared documentation folders become hard to navigate as they grow, and inconsistent frontmatter breaks discovery. This Skill scans a directory of Markdown docs, validates their metadata against a schema, and regenerates a single INDEX.md so other tools and agents can find relevant documents without reading every file. ## Core Features & Use Cases - Frontmatter validation: Checks required fields (title, type, status, owner, created) against the repository's type/status vocabulary, with a --fix mode that auto-fills inferrable values from git history and file stats. - INDEX.md generation: Writes a sorted, grep-friendly index with inline status, owner, and tag metadata; it is the sole writer of INDEX.md files. - Stale document auditing: The --stale flag surfaces expired docs or files untouched for over 90 days. - Use Case: After publishing several new runbooks to a shared knowledge base, run the index skill on that directory to validate their frontmatter and regenerate the INDEX.md so teammates and bots can discover them. ## Quick Start Ask the agent to run the index skill on your documentation directory, for example: index the docs/knowledge folder and fix any missing frontmatter fields.

Frequently Asked Questions about index

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

FAQPage Schema
How do I generate an index for a Markdown documentation folder?

Run the index skill with the target directory path as the argument. It walks all .md files, parses their frontmatter, and writes a sorted INDEX.md with titles, descriptions, status, owner, and tags for each document.

How to validate YAML frontmatter across many Markdown files?

Use the --validate-only flag to check required fields (title, type, status, owner, created) against the schema without regenerating INDEX.md. Each error is reported with file path, field name, and issue type.

Can missing frontmatter fields be filled in automatically?

Yes, the --fix flag auto-fills inferrable fields: created from file mtime or git history, owner from the last git author, status from type defaults, and type from the parent directory name. Only frontmatter is modified, never document content.

How do I find stale or expired documentation files?

Use the --stale flag to flag documents whose expires date has passed or whose created, updated, or last_verified dates are over 90 days old. Stale docs are reported separately from validation errors.

Why does the index skill refuse to index some directories?

Directories marked as engine-managed roots (annotated as a claudron vault or set via the engine environment variable) are never indexed, because the engine owns their indexing and a generated INDEX.md would be stale immediately.