chryzxcchryzxc/herm/.agents/skills/hermes-integration/SKILL.md

hermes-integration

Skill45 starsChanged 22 days agoMITView on GitHub

Add or change a Herm feature that talks to Hermes (JSON-RPC method, streamed event, or `hermes` CLI command). Use when wiring new runtime data or mutations into Herm.

In this repository2 other files it gives its agents.
- AGENTS.mdAGENTS.md
- verify-changeSkill

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Confirm the contract exists: Check ARCHITECTURE.md → Contracts and the existing callers in Sources/Herm/HermesRuntime/.
line 12
Distinctive:
Mutations: must be typed and explicitly confirmed.
line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Wiring Herm to Hermes

Herm is the front end only. Build features from existing Hermes RPCs, events and CLI output. Never patch ~/.hermes/hermes-agent or propose engine changes. If the contract you need does not exist, stop and tell the user.

Confirm the contract exists. Check ARCHITECTURE.md → Contracts and the existing callers in Sources/Herm/HermesRuntime/. For CLI, confirm the exact subcommand and flags against the installed hermes <cmd> --help.
Transport stays in HermesRuntime/. RPCs go through HermesControlRPC. Build CLI commands as quoted words in HermesCLIAdapter, never as interpolated strings.
Gate on capability. Gate the control on HermesCapabilityService probe terms, not just the --help exit code, and fail closed: when the capability is missing, show an unavailable state.
Project, don't own. Parse into DockModel/ControlCenterModel state. Hermes responses are authoritative. Do not show final state optimistically, and do not keep a second durable copy in WorkspaceStore.
Mutations must be typed and explicitly confirmed. They must state whether they affect the active session or only later sessions.
Errors go through HermesDiagnosticsService.safeSummary before display.
Tests: cover the parsing and state transitions, plus an adapter test that asserts the exact quoted-word command. Use fixtures; never call a live Hermes.
Generative UI: expose a feature only after its typed component/adapter is registered, availability is verified, its example passes contract tests, and actions reuse established handlers. Register connected record readers and resolvers together in RichHostActionRouter.Feature; the next submission's catalog derives from RichFeatureRegistry, not a second handwritten prompt. An RPC name alone does not establish a working generated interface.

Then follow verify-change.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free