nemoclaw-maintainer-evening

Runs the end-of-day NemoClaw release handoff and optionally cuts a release tag. Use for evening, handoff, wrap-up, or ship requests.

Quality

76%

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-maintainer-evening/SKILL.md

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 well-structured, actionable orchestration skill with a clear gated sequence for a destructive tag-cut operation. Its main weaknesses are minor redundancy across the show/report sections and external references that cannot be verified within this skill's own bundle.

Suggestions

De-duplicate the Section 3 'Show' list and Section 5 'report' list so the handoff items are stated once, trimming conciseness redundancy.

Move the shared version scripts (version-target.ts, version-progress.ts) into this skill's own scripts/ bundle or add a local reference so the actionability targets are self-contained.

Add a short pre-tag checklist mirroring the Hard Rules as explicit verification steps in Section 4 to lift workflow_clarity toward a feedback-loop structure.

Dimension	Reasoning	Score
Conciseness	The body is dense, procedural, and assumes competence with no padding about known concepts, but the 'Show' list in Section 3 and the 'report' list in Section 5 overlap, and the Hard Rules restate earlier inline prohibitions — minor over-explanation that keeps it below the lean anchor.	4 / 5
Actionability	It provides concrete runnable commands (version-target.ts / version-progress.ts invocations), specific sub-skill delegation, and exact paths, but uses vX.Y.Z placeholders and several 'show/report' directives rather than copy-paste-ready commands for every step, so it sits at 'mostly executable' rather than fully executable.	4 / 5
Workflow Clarity	The five numbered sections form a clear sequence with explicit validation gates ('Merge the documentation PR before selecting the tag candidate', 'Never cut a tag without the maintainer's exact confirmation phrase'), satisfying the destructive-operation requirement so the cap is not triggered; it falls below the top anchor only because tag verification and the error-recovery checklist are delegated to the sub-skill rather than embodied here.	4 / 5
Progressive Disclosure	It is a clear overview with well-signaled, one-level-deep markdown references (PR-REVIEW-PRIORITIES.md, release-train.md, CONTRIBUTING.md) and delegation to nemoclaw-maintainer-cut-release-tag, but the referenced materials live in sibling skills outside this bundle and no local references/scripts/assets files exist, leaving minor organization and resolvability gaps.	4 / 5
	Total	16 / 20 Passed

Description

78%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 description that clearly answers what and when with natural trigger phrases in a distinct niche. It could be sharpened by naming more concrete handoff actions and adding synonyms like 'end of day' or 'release'.

Suggestions

Enumerate one or two more concrete handoff actions (e.g., 'compiles the release entry, summarizes merged work, and reports E2E status') to lift specificity above the 1-2-action band.

Add common trigger synonyms such as 'end of day', 'release', 'tag', or 'sign-off' to broaden natural keyword coverage.

Tighten distinctiveness by pairing generic triggers ('ship', 'handoff') with the NemoClaw qualifier to reduce overlap with sibling release skills.

Dimension	Reasoning	Score
Specificity	Names the domain (NemoClaw release) and two concrete actions ('release handoff', 'optionally cuts a release tag') but does not comprehensively enumerate what the handoff entails, matching the '1-2 concrete actions' anchor rather than the 'several specific actions' anchor above.	3 / 5
Completeness	It explicitly states both what ('Runs the end-of-day NemoClaw release handoff and optionally cuts a release tag') and when ('Use for evening, handoff, wrap-up, or ship requests') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	The 'Use for evening, handoff, wrap-up, or ship requests' clause supplies four natural terms a user would actually say, giving good coverage; common synonyms like 'end of day', 'release', 'tag', or 'sign-off' are missing, so it falls just below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	The product-specific 'NemoClaw release handoff' niche is mostly distinct with minimal conflict risk, but generic triggers like 'ship' and 'handoff' could overlap with sibling release skills, keeping it just below the minimal-conflict anchor.	4 / 5
	Total	16 / 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: 3 suspicious	Warning

	Total	14 / 16 Passed

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