nemoclaw-maintainer-refactor-docs

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

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/Army161/NemoClaw --skill nemoclaw-maintainer-refactor-docs-army161
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-maintainer-refactor-docs
Source: https://github.com/Army161/NemoClaw/tree/main/.agents/skills/nemoclaw-maintainer-refactor-docs
Command: npx skills add https://github.com/Army161/NemoClaw --skill nemoclaw-maintainer-refactor-docs-army161

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 while preserving every fact, route, and redirect. ## Core Features & Use Cases - Information Architecture Redesign: Splits monolithic pages into one-topic-per-page structures with journey-based navigation (Choose, Set Up, Operate, Validate, Troubleshoot) and non-clickable grouping nodes in docs/index.yml. - URL Migration and Redirects: Builds route and anchor migration tables, adds direct redirects in fern/docs.yml, and updates inbound links across docs, README, tests, and release notes. - Canonical Ownership and Deduplication: Assigns each fact, procedure, and troubleshooting topic a single canonical owner, merging duplicates instead of leaving parallel copies. - Use Case: When the Inference docs section grows too large, use this Skill to inventory every heading, split provider setup flows into focused pages, move troubleshooting to Reference, add redirects for legacy URLs, and validate with the docs build and route tests. ## 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 plus unheaded prose blocks, map each to a canonical destination page, then create the new pages, move content, update navigation in docs/index.yml, and add redirects in fern/docs.yml. Validate with the docs build and route tests before deleting old files.

How do I migrate documentation URLs without breaking existing 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. Update inbound links in docs, README, tests, and release notes, and confirm no redirect chains exist.

Does this Skill support multiple agent documentation variants?

Yes, it handles OpenClaw, Hermes, and Deep Agents variants rendered from shared source pages via generated variant files. You edit the source page and navigation mapping, then regenerate variants and inspect the generated output for rendering issues.

When should I not use this docs refactor approach?

Avoid it for small wording fixes or single-page edits that do not change topic ownership, navigation, or URLs. The process is designed for bounded section-level refactors; adjacent cleanup outside the named section should be reported, not folded in.

How are documentation refactors validated after restructuring?

Run npm run docs:sync-agent-variants, npm run docs, the published-route and link vitest suites, and git diff --check. Then audit deleted filenames, old slugs, moved anchors, redirect termination, and duplicate troubleshooting headings.