hermes-compatibility-audit

Audits repository compatibility against the latest stable upstream hermes-agent release and official docs.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/GonkaGate/hermes-agent-setup --skill hermes-compatibility-audit-gonkagate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hermes-compatibility-audit
Source: https://github.com/GonkaGate/hermes-agent-setup/tree/main/.agents/skills/hermes-compatibility-audit
Command: npx skills add https://github.com/GonkaGate/hermes-agent-setup --skill hermes-compatibility-audit-gonkagate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It determines whether the hermes-agent-setup repository still matches the current stable upstream hermes-agent contract, catching config, provider, auth, or CLI drift that would make the documented GonkaGate setup plan stale or unsafe. ## Core Features & Use Cases - Primary-source auditing: Compares official Hermes docs, GitHub release tags, and tagged source against repository assumptions in README, docs, src, and tests. - Structured verdicts: Classifies findings as confirmed upstream change, confirmed compatible, repo-overstatement, or inferred risk, then returns a compatible, compatible-with-caveats, or incompatible verdict. - Read-only safety: Enforces isolated, non-mutating inspection so audits never touch the user's real ~/.hermes state. - Use Case: Before publishing a new release of the setup helper, run the audit to confirm that the latest hermes-agent stable release still supports the gonkagate custom-provider wiring and .env secret handling the repository documents. ## Quick Start Audit whether this repository is still compatible with the latest stable hermes-agent release and report any breaking upstream changes.

Frequently Asked Questions about hermes-compatibility-audit

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

FAQPage Schema
How do I check if my hermes-agent setup is still compatible with the latest release?

Run a compatibility audit that compares the latest stable hermes-agent release tag and official docs against the repository's documented config, provider, and CLI assumptions. The audit returns a verdict of compatible, compatible with caveats, or incompatible with cited evidence.

What sources does a hermes-agent compatibility audit use?

It uses primary sources only: official Hermes documentation, the GitHub releases page for the exact stable tag, and tagged upstream source or tests. Secondary summaries are avoided, and tagged source wins when docs disagree.

Does the audit modify my Hermes configuration or repository files?

No. The audit is strictly read-only and never runs upstream commands against the real ~/.hermes directory. Any CLI inspection happens in an isolated temporary directory with redirected HOME and HERMES_HOME paths.

Does the audit cover prerelease or main-branch hermes-agent changes?

Prerelease and main-branch signals are tracked only as a watchlist and excluded from the stable verdict. The compatibility decision is based solely on the latest stable release unless prerelease auditing is explicitly requested.

What happens when the audit finds an incompatibility?

The report names the exact repository surfaces that break, cites the confirmed upstream change, and lists minimal recommended fix areas. It does not design or apply a migration, keeping the audit a decision gate rather than a remediation tool.