nemoclaw-maintainer-refactor-docs

Refactors oversized NemoClaw Fern documentation sections into focused pages with redirects and navigation.

22.3k|3.1k|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-maintainer-refactor-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-maintainer-refactor-docs
Source: https://github.com/NVIDIA/NemoClaw/tree/main/.agents/skills/nemoclaw-maintainer-refactor-docs
Command: npx skills add https://github.com/NVIDIA/NemoClaw --skill nemoclaw-maintainer-refactor-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large documentation sections become hard to navigate and maintain as they accumulate topics, duplicate guidance, and tangled URLs. This Skill plans and executes maintainer-owned refactors of oversized NemoClaw Fern docs sections into focused one-topic pages while preserving every fact, route, and redirect.

Core Features & Use Cases

  • Information Architecture Redesign: Builds journey-based nested navigation (Choose, Set Up, Operate, Validate, Troubleshoot) with non-clickable group nodes in docs/index.yml.
  • Canonical Ownership and Deduplication: Assigns each fact, procedure, and failure mode to one canonical page, consolidating duplicate troubleshooting into the Reference section.
  • URL Migration and Redirects: Creates route and anchor migration tables, adds direct redirects in fern/docs.yml, and validates published routes with vitest checks.
  • Use Case: When the Inference docs section grows into a monolith, use this Skill to split it into per-task pages, move troubleshooting to Reference, add legacy redirects, and verify the build across OpenClaw, Hermes, and Deep Agents variants.

Quick Start

Ask the agent to refactor the oversized Inference documentation section into focused one-topic pages with updated navigation, redirects, and validation.

Frequently Asked Questions about nemoclaw-maintainer-refactor-docs

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

FAQPage Schema
How do I split a large documentation page into smaller pages?

Inventory every H2 and H3, map each block to a canonical owner page, then create destination pages before deleting sources. Update navigation in docs/index.yml, add direct redirects in fern/docs.yml, and validate with the docs build and route tests.

How do I reorganize a Fern docs table of contents?

Design a journey-based structure (Choose, Set Up, Operate, Validate, Troubleshoot) with non-clickable group nodes containing only section, slug, and contents. Keep one topic per page and reuse group slugs across agent variants.

How do I migrate documentation URLs without breaking links?

Build a route table mapping every old published route to its final destination, then add direct redirects in fern/docs.yml covering latest, non-latest, variant, and legacy .html forms. Never create redirect chains or link to non-clickable section nodes.

Does this docs refactor workflow support multiple agent variants?

Yes, it handles OpenClaw, Hermes, and Deep Agents variants. Shared pages render through generated variant files, so you edit source pages and navigation mappings, then regenerate variants and inspect the output for rendering issues.

When should I not use this docs refactor process?

Avoid it for small edits or single-page wording fixes that do not change structure, ownership, or URLs. It is designed for bounded section-level refactors where navigation, canonical ownership, or published routes change.