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.

The content is a tightly scoped, actionable release-notes workflow with real executable gh/git commands, a clear step sequence, and sensible validation and feedback paths. It is largely lean, with only minor redundancy between the inline steps and the Hard Rules section.

Suggestions

Trim redundancy between the Hard Rules section and earlier steps (e.g., contributor-affiliation and SHA/E2E exclusions are stated in Step 3 and again in Hard Rules) to recover tokens without losing the guardrails.

Make the Step 1/Step 2 verification checks explicit pass/fail gates (e.g., 'Abort and route to nemoclaw-maintainer-evening if the canonical changelog entry is missing') so checkpoints are enforced rather than implied.

Consider extracting the contributor-credit replay logic and example into a one-level reference file to keep the core Step sequence lean, since that subsection is the densest in the body.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence (no explaining git/gh/tag concepts), with substantive concrete commands throughout; the main over-explanation is the Hard Rules section, which restates several rules already covered in earlier steps.	4 / 5
Actionability	Provides copy-paste-ready, executable commands (git ls-remote, gh api compare with a full jq filter, gh pr view, the NVIDIA membership check loop) with clearly marked placeholders, plus a concrete Markdown example covering the common replay case.	5 / 5
Workflow Clarity	Steps 1-7 plus Prerequisites and Output form a clear, well-sequenced workflow with explicit confirmation checks (Step 1 range peel, Step 2 verify against live compare) and a feedback path for the missing-canonical-entry defect; a few checkpoints are implicit rather than enforced.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with a single, well-signaled one-level-deep reference (../_shared/documentation-writing-review.md) and no nested references; content is cohesive in one file, with minor organization gaps in the longer narrative/credit sections.	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.

The description is concise, specific, and clearly answers both what the skill does and when to invoke it, with concrete trigger phrases tied to a distinct maintainer niche. The only minor gap is that it describes a single primary action with strong input specificity rather than enumerating several distinct actions.

Dimension	Reasoning	Score
Specificity	Names a concrete action ('Drafts the post-tag NemoClaw Announcement') and concrete inputs ('from tag, compare, and release-entry data'), which is specific and not vague, though it centers on a single primary action rather than listing several.	4 / 5
Completeness	Explicitly answers both '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 trigger phrases.	5 / 5
Trigger Term Quality	Includes natural maintainer-facing triggers ('Use after tagging or when asked to summarize vX.Y.Z'), with good keyword coverage; a few common variations like 'release notes' or 'changelog' are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear, narrow niche (post-tag NemoClaw Announcement, vX.Y.Z) with distinct triggers and minimal overlap risk; it even distinguishes itself from sibling release skills by scoping to post-tag announcement drafting.	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: e94c06f

Reviewed: 5 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.