unheaded-librarian

Index and map the Unheaded documentation web across all layers.

2|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/unheaded/unheaded --skill unheaded-librarian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unheaded-librarian
Source: https://github.com/unheaded/unheaded/tree/main/skills/unheaded-librarian
Command: npx skills add https://github.com/unheaded/unheaded --skill unheaded-librarian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Librarian coordinates and enforces consistency across the Unheaded documentation web, ensuring every layer (CLAUDE.md, battle-plan.md, references, docs, wiki, and READMEs) stays in sync.

Core Features & Use Cases

  • Ripple updates across multiple layers when a feature is added, renamed, or restructured.
  • Generate wiki scaffolds from source docs and maintain GitHub wiki conventions (Home, _Sidebar, _Footer, wiki-links).
  • Validate frontmatter and cross-link references to keep the knowledge graph coherent.

Quick Start

Execute a cross-document update pass to map and align the current doc web before making edits.

Frequently Asked Questions about unheaded-librarian

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

FAQPage Schema
How do I keep markdown documentation consistent when renaming files across multiple directories?

Documentation consistency during file renames is maintained by indexing the entire doc web and applying synchronized ripple updates to every cross-reference, frontmatter field, and wiki link affected by the restructuring.

What is the best way to validate cross-references and frontmatter in a wiki?

Wiki cross-reference validation works by mapping all frontmatter fields and internal links across the documentation graph, then enforcing metadata accuracy and coordinated commit discipline to keep the knowledge base coherent.

How do I generate GitHub wiki scaffolds from existing markdown source docs?

GitHub wiki scaffolding is generated by extracting structure from source markdown docs to create and maintain standard wiki conventions including Home, _Sidebar, _Footer, and internal wiki-links automatically.

Can I automate coordinated updates across CLAUDE.md, battle-plan.md, and a docs folder?

Coordinated updates across CLAUDE.md, battle-plan.md, docs, and wiki directories are automated by mapping the documentation web and enforcing synchronized ripple changes with strict commit discipline whenever features are added or restructured.

When do I need to run a cross-document consistency check on my content management workflow?

A cross-document consistency check is needed before making edits to map and align the current documentation web, ensuring ripple changes from file renames or feature restructuring propagate accurately across all layers.

Does version control help with maintaining documentation cross-references in markdown?

Version control supports documentation cross-references by enforcing strict commit discipline during synchronized updates, ensuring every metadata change and ripple edit across the wiki is tracked and coordinated.