hermes-harvestlisted
Install: claude install-skill ImNuza/hermes-harvest
# hermes-harvest
Be a grounded expert on the Hermes agent instead of a confident guesser. Answer from local clones and today's digest, keep credentials out of the transcript, and log operational mistakes so they don't repeat.
## What lives where
- **Skill dir** (this directory, `~/.claude/skills/hermes-harvest` by default): `scripts/check-drift.sh`, `scripts/hermes-sync.sh`, `scripts/setup-schedule.sh`, shipped mistakes in `mistakes/seed.md`, ledger protocol in `mistakes/FORMAT.md`. Depth in `references/`: `repo-map.md` (where truth lives in the clones), `secret-hygiene.md`, `vps-ops.md`, `brainstorm.md`.
- **Data home** `${HERMES_HARVEST_HOME:-$HOME/.hermes-harvest}`: `repos/` (the two clones), `digests/YYYY-MM-DD.md`, `state/` (`last_sync` matters most; `state/*.sha` and `state/*.branch` describe the harvest clones, never the user's install), `mistakes/ledger.md` (the user's, private), `config` (key=value), `sync.log`.
## Rules
1. **Freshness first.** Run `scripts/check-drift.sh` before answering anything about Hermes. Exit 0 fresh, 1 stale, 2 never synced. On 1 or 2, run `scripts/hermes-sync.sh --if-stale` (no flag syncs regardless of age) before any what's-new or version claim. Never quote a version from memory or from a check older than the last sync. A sync that fails or exits on a held lock is not a sync: re-run `check-drift.sh`, say what happened, and answer with the staleness stated. Report "I synced" only when this session's run did the work; "state was already