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 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

92%

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

85%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 instruction-only workflow that sequences a dependency upgrade with strong validation and feedback loops, and cleanly offloads detail to one-level-deep references. The main weakness is mild verbosity and reliance on external references for executable specifics rather than minor correctness gaps.

Suggestions

Tighten the 'Mutation boundary' and 'Keep Point-in-Time Review Records out of the Repository' paragraphs to bullet-style directives to reduce token cost without losing the constraints.

Inline one or two concrete invocation patterns for the collector scripts (e.g. a representative command shape) so the most common path is executable without first opening the referenced files.

Add a brief inline example of a recorded concern (old/new contract + consumer + failure mode + migration) to make the 'Resolve concerns' steps immediately actionable rather than abstract.

Dimension	Reasoning	Score
Conciseness	Lean and directive throughout, assuming Claude's competence without explaining basic concepts; a few prose passages (e.g. the mutation-boundary and record-keeping paragraphs) could be tightened without losing meaning, so it stops just short of fully earning every token.	4 / 5
Actionability	Concrete numbered steps, checklists, and specific pointers (collect-release-ledger.py, release-ledger.md, hermes.md, contract-audit.md) plus precise controls (mode 0600, byte/record ceilings, absolute Git/gh paths) make the guidance actionable, though much of the executable detail is delegated to external references rather than given inline.	4 / 5
Workflow Clarity	A clear Plan → Discover → Audit → Resolve → Verify sequence with explicit validation checkpoints ('An unresolved high-impact concern blocks the upgrade', the 'Before handoff' checklist, rechecking identities) and a feedback loop where unresolved concerns block progression.	5 / 5
Progressive Disclosure	The body is a concise overview with well-signaled one-level-deep markdown links to real bundle files (references/release-ledger.md, references/hermes.md, references/contract-audit.md, scripts/collect-release-ledger.py) and shared/peer skills, with detail appropriately split out rather than inlined.	5 / 5
	Total	18 / 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.

An exemplary description: concrete actions, comprehensive natural trigger keywords, explicit what-and-when guidance, and a clearly distinct niche. Third-person voice is used throughout with no over-claims or fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Audit and implement a dependency upgrade', 'Trace upstream changes into current NemoClaw consumers', 'resolve security and lifecycle concerns', 'verify the artifacts' — with comprehensive coverage of the upgrade scope (library, CLI, service, image, runtime, installer artifact, transitive dependency).	5 / 5
Completeness	Explicitly answers both 'what' (audit/implement a dependency upgrade as a semantic migration, trace consumers, resolve concerns, verify artifacts) and 'when' ('Use when changing a library, CLI, service, image, runtime, installer artifact, or transitive dependency, including a Hermes release') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage with synonyms and variations: 'update dependency, upgrade dependency, bump version, dependency migration, release audit' plus dedicated Hermes triggers (update/upgrade/review Hermes, publish Hermes base image).	5 / 5
Distinctiveness Conflict Risk	A clear, narrow niche — NemoClaw dependency/Hermes upgrade migration — with distinct, specific triggers and minimal overlap risk 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: 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.