book-crosslink

Organize cross-book references and merge glossaries across mdBook projects.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/hafley66/claude-research --skill book-crosslink
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: book-crosslink
Source: https://github.com/hafley66/claude-research/tree/main/skills/book-crosslink
Command: npx skills add https://github.com/hafley66/claude-research --skill book-crosslink

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Connects multiple mdBook projects into a family with shared references, merged glossaries, and consolidated progress tracking across related books.

Core Features & Use Cases

  • Glossary merging: Terms from one book appear in sibling glossaries.
  • Cross-book references: Link concepts across books to aid navigation and understanding.
  • Shared crates and progress: Optional shared workspace and unified progress view for the family of books.
  • Use Case: When building a set of related documentation projects, maintain consistency and interoperability across all books within the family.

Quick Start

Set up a books.toml family registry and connect ml-through-rust and networking-through-rust.

Frequently Asked Questions about book-crosslink

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

FAQPage Schema
How do I link multiple mdBook projects into a single documentation family?

Set up a books.toml family registry to connect related mdBook projects, enabling shared glossaries, cross-book references, and consolidated progress tracking across the entire documentation family.

Can I share a glossary across multiple mdBook projects?

Yes, glossary merging lets terms from one mdBook automatically appear in sibling glossaries, maintaining terminology consistency across related books within the project family.

What is the best way to track progress across a family of mdBook projects?

Track progress across a family of mdBook projects using a books.toml registry that provides a unified progress view and optional shared workspace crates for the entire family.

How do cross-book references work in mdBook project families?

Cross-book references link concepts across related mdBook projects to aid navigation, allowing readers to jump directly between connected topics in sibling documentation books.

Do I need a books.toml file to merge dependencies across mdBook projects?

Yes, a books.toml family registry is required to merge dependencies and enable optional shared crates across multiple mdBook projects, serving as the central configuration for the project family.

When should I organize mdBook projects into a cross-book family?

Organize mdBook projects into a cross-book family when building related documentation that requires consistency, shared glossaries, and interoperability across multiple learning resources or technical books.