nemoclaw-contributor-update-docs

Find user-visible changes merged to NemoClaw and update their owning documentation. Use in the post-merge documentation workflow or for direct documentation catch-up. Derive pages, commands, variants, and validation from the current checkout. Trigger keywords - update docs, docs from commits, catch up docs, docs drift.

Quality

81%

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

75%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 tightly written, well-structured instruction skill that leans on shared references and sibling skills to stay lean, with a clear workflow and an explicit validation gate. Its main weakness is actionability: several core steps describe what to do without giving executable commands, search patterns, or templates to execute them.

Suggestions

Add concrete executable detail to the 'Find documentation impact' steps, e.g. example search commands or a grep/terminology pattern for locating the owning page.

Include an explicit error-recovery feedback loop in 'Validate and hand off' (validation fails -> fix -> re-run) to lift workflow clarity to a 5.

Inline one short acceptance-criterion or evidence-record example so the 'State the user outcome... and acceptance criterion' directive has a copy-paste template.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: it never explains what documentation or a semver tag is, and every line is actionable instruction with no padding.	5 / 5
Actionability	Guidance is concrete in places ('change only docs/, fern/docs.yml, and fern/assets/', 'Required PR checks run npm run docs') but most steps are high-level directives ('Decide whether supported user-visible behavior changed', 'Find the owning page by searching...') with no executable commands or templates, leaving gaps.	3 / 5
Workflow Clarity	A clear multi-step sequence exists (range, load authority, find impact, update, validate/hand off) with an explicit validation checkpoint ('Required PR checks run npm run docs') and the find-impact list, though error-recovery feedback loops are only implied.	4 / 5
Progressive Disclosure	Well-organized into clear sections that defer detail to one-level-deep shared references ([implementation-discovery.md], [documentation-writing-review.md]) and sibling skills; the only gap is that those references live outside this bundle and are not present here to verify.	4 / 5
	Total	16 / 20 Passed

Description

87%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.

A strong, specific description that clearly states what it does, when to use it, and supplies natural trigger keywords, all in third person. Minor gains are possible from adding a few synonyms/file cues and tightening the action list.

Dimension	Reasoning	Score
Specificity	Names several concrete actions ('Find user-visible changes', 'update their owning documentation', 'Derive pages, commands, variants, and validation from the current checkout') rather than vague verbs, with only minor coverage gaps around what 'update' concretely entails.	4 / 5
Completeness	Explicitly answers both what ('Find user-visible changes merged to NemoClaw and update their owning documentation') and when ('Use in the post-merge documentation workflow or for direct documentation catch-up', plus a concrete 'Trigger keywords' clause).	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ('update docs', 'docs from commits', 'catch up docs', 'docs drift') with good coverage, though it lacks synonyms or filename/extension cues that would round it out.	4 / 5
Distinctiveness Conflict Risk	The NemoClaw scoping, 'owning documentation' niche, and specific trigger phrases give it a clear niche distinct from generic docs skills, with minimal overlap risk.	5 / 5
	Total	18 / 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: 2 suspicious	Warning

	Total	15 / 16 Passed

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

Reviewed: about 3 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.