nemoclaw-contributor-update-dependencies

Audit and implement a dependency upgrade as a semantic migration. Use when changing a library, CLI, service, image, runtime, installer artifact, or transitive dependency, including a Hermes release. Trace upstream changes into current NemoClaw consumers, resolve security and lifecycle concerns, and verify the exact artifacts that NemoClaw uses. Trigger keywords - update dependency, upgrade dependency, bump version, dependency migration, release audit, update Hermes, upgrade Hermes, review Hermes release, publish Hermes base image.

Quality

96%

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

92%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 body is a lean, well-sequenced procedural workflow with explicit validation checkpoints and a clean one-level-deep reference structure; its only weakness is the absence of copy-paste executable commands in the body, which requires reading the bundled scripts for exact invocations.

Suggestions

Include one or two concrete example invocations of collect-release-ledger.py (or a pointer to its --help output shape) so the body is actionable without first opening the script.

Add a short worked example of a completed concern record (filled DEP-<number> template) inline or in contract-audit.md to make the resolve-concerns step immediately executable.

Surface the exact selector/pin command or snippet for Hermes base-image publication in hermes.md so the publish step can be executed without re-deriving the command.

Dimension	Reasoning	Score
Conciseness	Terse imperative style with no concept over-explanation ('Treat an upgrade as a migration, not a version edit', 'Change only the NVIDIA/NemoClaw checkout in scope'); every section is task-relevant policy or procedure with no padding.	5 / 5
Actionability	Provides concrete numbered steps, named scripts (collect-release-ledger.py), named paths (internal/security-reviews/), and a concern-record template in the references, but the body itself contains no copy-paste executable commands — the reader must inspect each script's --help for exact invocations.	4 / 5
Workflow Clarity	Clear sequence (Plan → Discover → Audit → Resolve → Verify) with explicit validation checkpoints, a blocking condition ('An unresolved high-impact concern blocks the upgrade'), and a 'Before handoff' checklist covering recheck, disposition, selector agreement, and gate separation.	5 / 5
Progressive Disclosure	Overview body points to three one-level-deep references (release-ledger.md, hermes.md, contract-audit.md) and two scripts, each clearly signaled with its purpose; the references do not nest further into document chains, so navigation is easy.	5 / 5
	Total	19 / 20 Passed

Description

100%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 strong across all dimensions: concrete actions, an explicit Use-when clause, comprehensive natural trigger keywords, and a distinct niche anchored to dependency upgrades and Hermes releases.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'Audit and implement a dependency upgrade as a semantic migration', 'Trace upstream changes into current NemoClaw consumers', 'resolve security and lifecycle concerns', and 'verify the exact artifacts that NemoClaw uses' — covering the upgrade lifecycle comprehensively.	5 / 5
Completeness	Clearly states what ('audit and implement a dependency upgrade as a semantic migration', trace, resolve, verify) and an explicit 'Use when changing a library, CLI, service, image, runtime, installer artifact, or transitive dependency' clause, supplemented by concrete trigger phrases.	5 / 5
Trigger Term Quality	Explicit 'Trigger keywords' list covers natural phrases users would say — 'update dependency', 'upgrade dependency', 'bump version', 'release audit' — plus Hermes-specific synonyms ('update Hermes', 'upgrade Hermes', 'review Hermes release', 'publish Hermes base image').	5 / 5
Distinctiveness Conflict Risk	The semantic-migration framing, NemoClaw consumer scope, and Hermes-specific triggers carve a clear niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	20 / 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: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: NVIDIA/NemoClaw
Path: .agents/skills/nemoclaw-contributor-update-dependencies/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.