nemoclaw-contributor-update-hermes

Audits, implements, and validates Hermes Agent version upgrades in the NemoClaw repository.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/Army161/NemoClaw --skill nemoclaw-contributor-update-hermes-army161
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-contributor-update-hermes
Source: https://github.com/Army161/NemoClaw/tree/main/.agents/skills/nemoclaw-contributor-update-hermes
Command: npx skills add https://github.com/Army161/NemoClaw --skill nemoclaw-contributor-update-hermes-army161

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Upgrading the pinned Hermes Agent dependency in NVIDIA/NemoClaw is risky: CalVer release tags, annotated tag identity, downstream compatibility patches, durable SQLite state, and base-image publication all must be audited and kept consistent, and a naive version bump can silently change security defaults or break runtime contracts. ## Core Features & Use Cases - Release identity resolution: Reconciles authoritative NousResearch/hermes-agent GitHub releases with a local clone, validating annotated tag objects, peeled commits, and adjacent CalVer ranges via the collect-hermes-release-supplement.py script. - Contract auditing: Maps every upstream change through NemoClaw surfaces including generated config, wrapper flags, compatibility patches, durable state, packaging, and runtime behavior using the Hermes contract map reference. - Image build and publication workflow: Guides exact-tag source pinning, BuildKit base and final image builds, base-image workflow dispatch, and immutable multi-platform digest pinning. - Use Case: A maintainer upgrading Hermes from v2026.7.7 to v2026.7.7.2 uses this Skill to audit the release range, retarget patches, rebuild the base image, and produce an approval-ready PR. ## Quick Start Use the nemoclaw-contributor-update-hermes skill to audit and deliver the Hermes upgrade to the target tag end to end.

Frequently Asked Questions about nemoclaw-contributor-update-hermes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade the Hermes Agent version in NemoClaw?

Run scripts/update-hermes-agent.sh with an explicit reviewed tag, audit the adjacent release range against the contract map, rebuild the base image without cache, then publish the branch base image and pin its immutable digest in the final Dockerfile.

How do I audit Hermes CalVer releases before an upgrade?

Capture the paginated GitHub releases and tag-refs APIs with gh, then run the collect-hermes-release-supplement.py script against a complete local clone. It validates annotated tags, peeled commits, ancestry, and adjacent ranges for three-or-more-component CalVer tags.

Why does the generic release collector miss some Hermes releases?

The generic collector parses strict three-component SemVer, so four-component CalVer tags like v2026.7.7.2 are omitted. The Hermes supplement script reconciles the authoritative stable release list and preserves those numeric CalVer endpoints.

Can I use the update script with its default tag or --rebuild flag?

No. The moving default must not be used for the final PR, and --rebuild implies --update-installed-copies, which modifies ~/.nemoclaw, ~/.hermes, and NEMOCLAW_SOURCE_ROOT. Both require explicit authorization for host-visible changes.

What must pass before a Hermes upgrade PR is approval-ready?

All active selectors must name the same reviewed release, every release-range concern needs a disposition, retained workarounds must pass against target source and runtime, the base-image workflow must publish both platforms, and the final Dockerfile must pin the immutable digest with exact-head CI green.