Injects navigation tables from nav.json into Markdown files in documentation suites.
npx skills add https://github.com/fabioc-aloha/tldr --skill nav-inject
Please help me install this Agent Skill. Skill: nav-inject Source: https://github.com/fabioc-aloha/tldr/tree/main/.github/skills/nav-inject Command: npx skills add https://github.com/fabioc-aloha/tldr --skill nav-inject
Injects a consistent navigation table into every Markdown file within a documentation suite, eliminating manual cross-link maintenance and drift.
Run the injector in your docs directory to stamp navigation tables into all Markdown files.
High-intent search queries and answers about installing and using this skill.
The mechanism uses nav markers as sentinels in your Markdown files to inject navigation tables non-destructively. It locates these sentinels, inserts the generated content between them, and preserves all surrounding material during updates.
You add cross-document navigation non-destructively by placing nav markers in your files so the injector can update content between sentinels. This approach preserves surrounding material while re-injecting the navigation table as needed.
Yes, you can use a simple nav.json configuration to define documents, labels, and icons for your Markdown navigation. The injector reads this configuration to generate consistent cross-document navigation tables across your suite.
The best way to maintain consistent cross-linking in a multi-file documentation set is automating the injection of navigation tables. This ensures global navigation remains uniform across governance, guides, and specifications without manual edits.
You should avoid automated navigation injection if your documentation is not a multi-file suite or lacks consistent nav markers. The tool relies on sentinels and a nav.json configuration to preserve surrounding material during non-destructive updates.
javierhbrDocument existing platform state and draft a baseline for Spec-Driven Development.
georgekhananaevEnforce consistent Markdown syntax across documentation and README files.
SireJeffValidate context engineering documentation structure, schemas, links, placeholders, and line numbers.
dogekikiConvert Markdown and JSON artifacts into single-file HTML documents.
