# Hermes

TEAM: one command installs the seven workers' files; you open each session yourself and carry the handoffs between them. Researcher goes first.

Check project trust and the installed client's loading controls before starting.
Manual SOLO: copy the complete canonical folder into a new `.agents/skills/website-build-skill/` in the chosen project.
For explicit loading, ask the session to read its SKILL.md directly.
After confirming the installed CLI supports it, try preload: `hermes -s website-build-skill` after discovery is confirmed.
After checking the installed CLI help, use its trust operation: `hermes skills trust`; this changes trust state and requires the user's authorization.
Do not create version-control state or alter global settings during a copy.
Install the files: `npx website-build-skill --team --target hermes --dir . --scope project --yes --bundle-dir team-aliases`.
The path is relative to the installed skill folder, so the alias files land in `.agents/skills/website-build-skill/team-aliases/` and the path must stay inside that folder.

## Open the workers

Open seven separate sessions yourself, Researcher first. Supply each complete role body
from `.agents/skills/website-build-skill/roles/`, the linked resources and its current handoff.
The `team-aliases` directory holds copies of the five bundles. An alias loads instructions;
verify each worker through its own session reference and carry the handoffs yourself.
Use [the team relay](grok.md#manual-fallback) and check each worker can read the assigned
revision, including any uncommitted files it needs. Check Reviewer permissions on inherited
tools; use a read-only packet and returned findings when needed.

## Shared core and receipt

Codex and Hermes candidate paths overlap. Compare content before writing and preserve conflicts.
Test installation in both orders, partial receipts and reference ownership before supporting shared uninstall.
An explicit bundle directory authorizes only that destination. Never write a home-directory alias implicitly.
The receipt enumerates core files, bundles, alias copies, hashes, mode and pending integration.

## Settling checks

Verify project trust before/after explicit authorization, native preload, all manifest assets and each session reference.
Verify seven acknowledgements, source-preserving relay, no downstream work before research and denied Reviewer writes.
Probe image, browser, execution and independent-family access separately.
Source targets: [skills](https://hermes-agent.nousresearch.com/docs/user-guide/features/skills), [delegation](https://hermes-agent.nousresearch.com/docs/user-guide/features/delegation), [CLI](https://hermes-agent.nousresearch.com/docs/user-guide/cli).


## Check that it loaded

Native loading on this host is awaiting a real-client trial; the check below confirms it on yours. Current status: [compatibility](../docs/COMPATIBILITY.md).

Give the host a synthetic brief and ask it to identify the entrypoint and complete asset list.
Record client version, date, exact path, tool availability and the observed invocation.
Start Researcher, verify saved library read-back, then confirm Coordinator waits for its gate.
For TEAM, record seven separate routes and families; an inherited family leaves independent review BLOCKED.
Never grant a Reviewer write access just to persist findings. Return text for Coordinator to capture.
When a tool is absent, keep current research BLOCKED until opened sources return; save and reattach named file bodies before the save gate; return inspected images before the visual gate.
Read the [method](../docs/METHOD.md), [compatibility](../docs/COMPATIBILITY.md) and [installer contract](../docs/INSTALLER.md).