nemoclaw-maintainer-refactor-docs

Plan and execute maintainer-owned refactors of oversized NemoClaw Fern documentation sections into focused one-topic pages with concise prose, journey-based nested navigation, non-clickable group nodes, canonical troubleshooting and reference ownership, deduplicated content, variant-aware route-style links, and complete redirects. Use when a docs page or section has grown too large, when reorganizing documentation information architecture or a table of contents, when splitting pages, shortening dense paragraph blocks, moving content across sections, consolidating duplicate guidance, or migrating URLs in docs/index.yml and fern/docs.yml. Trigger keywords - refactor docs, reorganize docs, split docs, nested TOC, documentation IA, one topic per page, big paragraphs, move troubleshooting, deduplicate docs, docs too long.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, well-sequenced instruction skill with concrete commands, file paths, and table templates, plus explicit validation and review checkpoints. Its main weakness is the absence of progressive disclosure into separate reference files for the detailed rule lists.

Suggestions

Move the detailed route rules and Step 7 audit checklist into a reference file (e.g. references/route-migration-rules.md) and link to it from the body to improve progressive disclosure.

Tighten the overlap between the per-step rules and the Completion Contract so the checklist references rather than restates them, reducing redundancy.

Provide one concrete worked example of a completed ownership inventory and route table (possibly in a referenced examples file) to ground the abstract table templates.

Dimension	Reasoning	Score
Conciseness	The body is dense but lean for its complexity — no explanations of basic concepts Claude already knows, and it assumes competence; minor redundancy between the step rules and the Completion Contract checklist keeps it just below the top anchor.	4 / 5
Actionability	Provides concrete executable commands (`npm run docs`, `npx vitest run ...`, `rg -n ...`), specific file paths (`docs/index.yml`, `fern/docs.yml`, `docs/reference/troubleshooting.mdx`), and ready-to-fill table templates (ownership inventory, route table, anchor migration), covering the common cases.	5 / 5
Workflow Clarity	Eight explicitly sequenced steps with dedicated validation (Step 7), an independent review loop (Step 8), and a Completion Contract checklist — clear feedback loops for destructive batch operations like page deletion and redirects.	5 / 5
Progressive Disclosure	Well-organized into clearly labeled sections with no nested references, but at 233 lines all detailed rule lists live inline with no split into separate reference files, leaving a minor organization gap versus the top anchor.	4 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a high-quality description that concretely states capabilities, provides explicit 'Use when' guidance, and includes natural trigger keywords with good synonym coverage. Its only mild weakness is verbosity, but every clause earns its place with specific, distinctive content.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'focused one-topic pages', 'journey-based nested navigation', 'non-clickable group nodes', 'canonical troubleshooting and reference ownership', 'variant-aware route-style links', 'complete redirects' — with comprehensive coverage of the refactor scope.	5 / 5
Completeness	Clearly answers 'what' (plan and execute maintainer-owned refactors...) and explicitly answers 'when' via a 'Use when...' clause plus concrete trigger keywords, matching the top anchor.	5 / 5
Trigger Term Quality	Trigger keywords 'refactor docs, reorganize docs, split docs, nested TOC, documentation IA, one topic per page, big paragraphs, move troubleshooting, deduplicate docs, docs too long' are natural phrases users would say, with strong synonym coverage.	5 / 5
Distinctiveness Conflict Risk	Targets a clear niche — NemoClaw Fern documentation IA refactoring — with distinct, specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: NVIDIA/NemoClaw
Path: .agents/skills/nemoclaw-maintainer-refactor-docs/SKILL.md
Commit: e987b00

Reviewed: about 4 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.