The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
docs: add hermes setup guide
Affaan Mustafab6d15b42f2aa
diff --git a/WORKING-CONTEXT.md b/WORKING-CONTEXT.mdindex 49906e48e..688c65b97 100644--- a/WORKING-CONTEXT.md+++ b/WORKING-CONTEXT.md@@ -164,3 +164,4 @@ Keep this file detailed for only the current sprint, blockers, and next actions.- 2026-04-05: Selectively salvaged `skills/frontend-design` from the Hermes branch as a self-contained ECC-native skill, mirrored it into `.agents`, wired it into `framework-language`, and re-synced the catalog to `180` skills after validation. The branch itself remains reference-only until every remaining unique file is either ported intentionally or rejected.- 2026-04-05: Selectively salvaged the `hookify` command bundle plus the supporting `conversation-analyzer` agent from the Hermes branch. `hookify-rules` already existed as the canonical skill; this pass restores the user-facing command surfaces (`/hookify`, `/hookify-help`, `/hookify-list`, `/hookify-configure`) without pulling in any external runtime or branch-wide regressions. Catalog truth is now `40` agents, `77` commands, and `180` skills.- 2026-04-05: Selectively salvaged the self-contained review/development bundle from the Hermes branch: `review-pr`, `feature-dev`, and the supporting analyzer/architecture agents (`code-architect`, `code-explorer`, `code-simplifier`, `comment-analyzer`, `pr-test-analyzer`, `silent-failure-hunter`, `type-design-analyzer`). This adds ECC-native command surfaces around PR review and feature planning without merging the branch's broader regressions. Catalog truth is now `47` agents, `79` commands, and `180` skills.+- 2026-04-05: Ported `docs/HERMES-SETUP.md` from the Hermes branch as a sanitized operator-topology document for the migration lane. This is docs-only support for `#1051`, not a runtime change and not a sign that the Hermes branch itself is mergeable.diff --git a/docs/HERMES-SETUP.md b/docs/HERMES-SETUP.mdnew file mode 100644index 000000000..aaefb1ba7--- /dev/null+++ b/docs/HERMES-SETUP.md@@ -0,0 +1,110 @@+# Hermes x ECC Setup++Hermes is the operator shell. ECC is the reusable system behind it.++This guide is the public, sanitized version of the Hermes stack used to run content, outreach, research, sales ops, finance checks, and engineering workflows from one terminal-native surface.++## What Ships Publicly++- ECC skills, agents, commands, hooks, and MCP configs from this repo+- Hermes-generated workflow skills that are stable enough to reuse+- a documented operator topology for chat, crons, workspace memory, and distribution flows+- launch collateral for sharing the stack publicly++This guide does not include private secrets, live tokens, personal data, or a raw `~/.hermes` export.++## Architecture++Use Hermes as the front door and ECC as the reusable workflow substrate.++```text+Telegram / CLI / TUI+ ↓+ Hermes+ ↓+ ECC skills + hooks + MCPs + generated workflow packs+ ↓+ Google Drive / GitHub / browser automation / research APIs / media tools / finance tools+```++## Public Workspace Map++Use this as the minimal surface to reproduce the setup without leaking private state.++- `~/.hermes/config.yaml`+ - model routing+ - MCP server registration+ - plugin loading+- `~/.hermes/skills/ecc-imports/`+ - ECC skills copied in for Hermes-native use+- `skills/hermes-generated/`+ - operator patterns distilled from repeated Hermes sessions+- `~/.hermes/plugins/`+ - bridge plugins for hooks, reminders, and workflow-specific tool glue+- `~/.hermes/cron/jobs.json`+ - scheduled automation runs with explicit prompts and channels+- `~/.hermes/workspace/`+ - business, ops, health, content, and memory artifacts++## Recommended Capability Stack++### Core++- Hermes for chat, cron, orchestration, and workspace state+- ECC for skills, rules, prompts, and cross-harness conventions+- GitHub + Context7 + Exa + Firecrawl + Playwright as the baseline MCP layer++### Content++- FFmpeg for local edit and assembly+- Remotion for programmable clips+- fal.ai for image/video generation+- ElevenLabs for voice, cleanup, and audio packaging+- CapCut or VectCutAPI for final social-native polish++### Business Ops++- Google Drive as the system of record for docs, sheets, decks, and research dumps+- Stripe for revenue and payment operations+- GitHub for engineering execution+- Telegram and iMessage-style channels for urgent nudges and approvals++## What Still Requires Local Auth++These stay local and should be configured per operator:++- Google OAuth token for Drive / Docs / Sheets / Slides+- X / LinkedIn / outbound distribution credentials+- Stripe keys+- browser automation credentials and stealth/proxy settings+- any CRM or project system credentials such as Linear or Apollo+- Apple Health export or ingest path if health automations are enabled++## Suggested Bring-Up Order++1. Install ECC and verify the baseline harness setup.+2. Install Hermes and point it at ECC-imported skills.+3. Register the MCP servers you actually use every day.+4. Authenticate Google Drive first, then GitHub, then distribution channels.+5. Start with a small cron surface: readiness check, content accountability, inbox triage, revenue monitor.+6. Only then add heavier personal workflows like health, relationship graphing, or outbound sequencing.++## Why Hermes x ECC++This stack is useful when you want:++- one terminal-native place to run business and engineering operations+- reusable skills instead of one-off prompts+- automation that can nudge, audit, and escalate+- a public repo that shows the system shape without exposing your private operator state++## Public Preview Scope++ECC 2.0 preview documents the Hermes surface and ships launch collateral now.++The remaining private pieces can be layered later:++- additional sanitized templates+- richer public examples+- more generated workflow packs+- tighter CRM and Google Workspace integrations