nemoclaw-maintainer-release-notes

Drafts the post-tag NemoClaw Announcement from tag, compare, and release-entry data. Use after tagging or when asked to summarize vX.Y.Z.

Quality

85%

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

Quality

Content

82%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 well-structured, highly actionable release-note drafting workflow with concrete gh/git commands and clear sequencing. The main improvement is reducing redundancy between the step guidance and the Hard Rules recap.

Suggestions

Consolidate the Hard Rules section so it references rather than restates the guidance already given in Steps 3 and 5 (memory-only drafting, external-only thanks, no affiliation), trimming conciseness redundancy.

Add an explicit validation/retry checkpoint in Step 2 for the case where live compare data contradicts the canonical changelog entry, stating how to reconcile or escalate.

Signal the external shared contract reference more prominently (e.g. in Prerequisites) so the dependency on ../_shared/documentation-writing-review.md is discoverable before the workflow begins.

Dimension	Reasoning	Score
Conciseness	The body is mostly procedural with executable commands and no padding about what git/gh is, but the Hard Rules section recapitulates guidance already stated in the steps (memory-only drafting, external-only thanks, affiliation), which is a minor redundancy that could be trimmed, fitting the 4 anchor rather than the fully lean 5.	4 / 5
Actionability	Steps provide copy-paste-ready, executable commands ("git ls-remote ...", "gh api repos/NVIDIA/NemoClaw/compare/... --jq ...", "gh pr view ... --json ...") plus a concrete markdown example, covering the common cases and matching the 5 anchor.	5 / 5
Workflow Clarity	Steps 1-7 are clearly sequenced with a "Confirm:" checkpoint in Step 1 and a verify-against-live-data instruction in Step 2, but there is no explicit validate-fix-retry feedback loop; the task is non-destructive so the 3-cap does not apply, placing this at the 4 anchor.	4 / 5
Progressive Disclosure	The single-file body is well-organized into Prerequisites, numbered Steps, Output, and Hard Rules, and the one external reference ("../_shared/documentation-writing-review.md") is clearly signaled and one level deep; with no bundle files to split and a minor organization gap from the duplicated Hard Rules recap, it sits at 4 rather than 5.	4 / 5
	Total	17 / 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, third-person description that clearly states both the task and the trigger conditions with specific, natural language. Minor specificity gains are available by enumerating more distinct drafting actions or adding 'release notes' as a synonym.

Dimension	Reasoning	Score
Specificity	Quotes "Drafts the post-tag NemoClaw Announcement from tag, compare, and release-entry data" name a concrete action and three specific data sources, but stop just short of enumerating multiple distinct drafting actions, matching the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.	4 / 5
Completeness	It explicitly answers what ("Drafts the post-tag NemoClaw Announcement from tag, compare, and release-entry data") and when ("Use after tagging or when asked to summarize vX.Y.Z") with concrete triggers, matching the 5 anchor; it is not the 4 anchor because the 'when' is specific rather than vague.	5 / 5
Trigger Term Quality	Phrases "Use after tagging or when asked to summarize vX.Y.Z" supply natural trigger language a maintainer would say, with good keyword coverage; a few common variations (e.g. 'release notes', 'announcement') are absent, so it sits at 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The niche "NemoClaw Announcement" plus "post-tag" and "vX.Y.Z" triggers are highly specific with minimal overlap risk, fitting the 'clear niche with distinct triggers' 5 anchor rather than the 'mostly distinct' 4 anchor.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: NVIDIA/NemoClaw
Path: .agents/skills/nemoclaw-maintainer-release-notes/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.