Update lifecycle
The hub now tracks enough provenance to re-check upstream copies of installed skills: This uses the stored source identifier plus the current upstream bundle content hash to detect drift. Checks skip network requests for missing or non-directory installs ( orphaned ) and unsafe or unresolvable recorded paths ( invalid_install ). Missing-directory entries can be removed with hermes skills uninstall <name> ; invalid paths require inspecting and repairing the active profile's skills/.hub/lock.json before retrying. No entries are removed automatically. Valid installs continue to use their source adapter's existing synchronous fetch and transport timeouts. There is no strict total deadline for an update check: an unreachable or slow source for an existing install can still delay later entries. Skills you have edited locally (the on-disk content no longer matches the hash recorded at install time) are skipped by hermes skills update so your changes are never silently overwritten. Pass --force to replace them with the upstream version anyway. GitHub rate limits Skills hub operations use the GitHub API, which has a rate limit of 60 requests/hour for unauthenticated users. If you see rate-l…
From the official Hermes Agent documentation.
hermes skills check # Report which installed hub skills changed upstream
hermes skills update # Reinstall only the skills with updates available
hermes skills update react # Update one specific installed hub skill
hermes skills update react --force # Overwrite a skill you've edited locally