How do I install the Contributor Docs Nav skill?

Run npx skillmds@latest add adobe/contributor-docs-nav in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Contributor Docs Nav safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Contributor Docs Nav?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Contributor Docs Nav free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Contributor Docs Nav?

Adobe (@adobe) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Contributor Docs Nav by adobe — Agent Skill

Name: Contributor Docs Nav
Author: Adobe

Contributor Docs Nav

Run the CONTRIBUTOR-DOCS nav script to update breadcrumbs and TOCs, and handle link verification. Use when updating contributor docs structure, regenerating navigation, or fixing broken links.

Adobe de08f35 2 files · 13.4 KB Updated Sep 17, 2026 142 repo stars

File contents

Contributor docs navigation

Run the regeneration script to update breadcrumbs and TOCs in CONTRIBUTOR-DOCS, and handle link verification. Two roles apply: Operator (run the script, fix link errors) and Maintainer (update the script when requirements change).

Mindset

You are a documentation maintainer. Broken links and stale navigation are bugs, not inconveniences. Never mark work done until every link is verified.

When to use this skill

A file or folder under CONTRIBUTOR-DOCS is added, removed, renamed, or moved
Document H1, H2, or H3 headings are changed
The user asks to update contributor docs navigation, regenerate TOC, or fix broken links in CONTRIBUTOR-DOCS
The contributor-doc-update rule is triggered (editing CONTRIBUTOR-DOCS structure)

How to invoke

Say "update contributor docs nav", "regenerate TOC", "fix broken links in CONTRIBUTOR-DOCS", or "run the nav script"
Or add, remove, rename, or move files under CONTRIBUTOR-DOCS/ or change H1/H2/H3 headings — the agent should run the nav script and may use this skill

Quick reference

Operator: run the script

When to run: File/folder add/remove/rename/move; heading changes; folder structure changes; or user request.

How to run (from project root):

cd CONTRIBUTOR-DOCS/01_contributor-guides/07_authoring-contributor-docs
node update-nav.js

After running: Verify success, report results (files updated, link counts). Fix straightforward link errors automatically; ask the user when the fix is ambiguous (e.g. target file removed, multiple anchor matches).

Maintainer: update the script

When: Naming/convention changes, breadcrumb/TOC format changes, new edge cases, or display-name rule changes.
Process: Review change → update update-nav.js → test on full tree → update docs and report.

Full instructions

For complete Operator and Maintainer workflows, debugging, link-verification handling, script behavior details, and the testing checklist, read:

.ai/skills/contributor-docs-nav/references/ai-agent-instructions.md

That document is the single source of truth for when to run, how to run, responsibilities, debugging, handling link verification errors, maintainer process, script architecture, and testing checklist.

---name: contributor-docs-navdescription: Run the CONTRIBUTOR-DOCS nav script to update breadcrumbs and TOCs, and handle link verification. Use when updating contributor docs structure, regenerating navigation, or fixing broken links.---# Contributor docs navigationRun the regeneration script to update breadcrumbs and TOCs in CONTRIBUTOR-DOCS, and handle link verification. Two roles apply: **Operator** (run the script, fix link errors) and **Maintainer** (update the script when requirements change).## MindsetYou are a documentation maintainer. Broken links and stale navigation are bugs, not inconveniences. Never mark work done until every link is verified.## When to use this skill- A file or folder under CONTRIBUTOR-DOCS is added, removed, renamed, or moved- Document H1, H2, or H3 headings are changed- The user asks to update contributor docs navigation, regenerate TOC, or fix broken links in CONTRIBUTOR-DOCS- The contributor-doc-update rule is triggered (editing CONTRIBUTOR-DOCS structure)## How to invoke- Say "update contributor docs nav", "regenerate TOC", "fix broken links in CONTRIBUTOR-DOCS", or "run the nav script"- Or add, remove, rename, or move files under `CONTRIBUTOR-DOCS/` or change H1/H2/H3 headings — the agent should run the nav script and may use this skill## Quick reference### Operator: run the script1. **When to run**: File/folder add/remove/rename/move; heading changes; folder structure changes; or user request.2. **How to run** (from project root): ```bash cd CONTRIBUTOR-DOCS/01_contributor-guides/07_authoring-contributor-docs node update-nav.js ```3. **After running**: Verify success, report results (files updated, link counts). Fix straightforward link errors automatically; ask the user when the fix is ambiguous (e.g. target file removed, multiple anchor matches).### Maintainer: update the script- **When**: Naming/convention changes, breadcrumb/TOC format changes, new edge cases, or display-name rule changes.- **Process**: Review change → update `update-nav.js` → test on full tree → update docs and report.## Full instructionsFor complete Operator and Maintainer workflows, debugging, link-verification handling, script behavior details, and the testing checklist, read:**.ai/skills/contributor-docs-nav/references/ai-agent-instructions.md**That document is the single source of truth for when to run, how to run, responsibilities, debugging, handling link verification errors, maintainer process, script architecture, and testing checklist.

Frequently asked questions