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

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/nemoclaw-contributor-update-docs/SKILL.md

Quality

Content

67%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 concise, well-structured instruction-only workflow with a clear sequence and validation, appropriately leaning on shared contracts rather than re-explaining concepts. Main gap is actionability: several core steps remain high-level directives rather than concrete, executable procedures.

Suggestions

Make the 'Find documentation impact' steps more executable: give concrete search entry points (e.g., specific grep patterns or file globs to locate owning pages) instead of 'searching current terminology, commands, configuration keys…'.

Add an explicit validation feedback loop for the direct-task path: 'run npm run docs; if it fails, fix the reported links/variants and re-run until clean' rather than only stating that checks run.

Tighten or relocate the boundary-handling prose (e.g., the managed-draft extension rules) so the authoring steps read as a leaner checklist.

Dimension	Reasoning	Score
Conciseness	Lean imperative prose with no concept over-explanation or padding; a few elaborative clauses ('Do not advance either boundary while authoring') could be trimmed, keeping it just below the top anchor.	4 / 5
Actionability	Concrete specifics exist (docs/**, fern/docs.yml, npm run docs, semver-tag-to-main range) but many steps are high-level directives ('Decide whether supported user-visible behavior changed', 'Find the owning page by searching…') and execution delegates heavily to external shared contracts.	3 / 5
Workflow Clarity	Clear sectioned sequence with a numbered impact list and a validation step (npm run docs, inspect variants/links); not 5 because no explicit validate→fix→retry feedback loop is specified.	4 / 5
Progressive Disclosure	Well-organized sections with clearly signaled one-level-deep references (../_shared/implementation-discovery.md, ../_shared/documentation-writing-review.md) and no nested references; not 5 because some inlined guidance overlaps content the shared contracts already cover.	4 / 5
	Total	15 / 20 Passed

Description

83%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, well-scoped description that answers both what and when with concrete, natural trigger keywords and a distinct niche. Slightly held back from top marks by abstract action phrasing and minor overlap risk with sibling nemoclaw doc skills.

Dimension	Reasoning	Score
Specificity	Names several concrete actions ('Find user-visible changes… and update their owning documentation', 'Derive pages, commands, variants, and validation from the current checkout'); not 5 because 'derive pages/commands/variants' stays somewhat abstract compared to the granular-action anchor.	4 / 5
Completeness	Clearly states both what ('Find user-visible changes… update their owning documentation') and when ('Use in the post-merge documentation workflow or for direct documentation catch-up') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Explicit natural phrases ('update docs, docs from commits, catch up docs, docs drift') give good keyword coverage; not 5 because it lacks the broader synonym/extension-style breadth of the top anchor.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (NemoClaw post-merge docs) with distinct triggers, but the body names sibling maintainer skills indicating minor overlap risk with closely related skills.	4 / 5
	Total	17 / 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: e94c06f

Reviewed: 4 days 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.