chore: checkpoint hermes-generated ops skills

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

docs/releases/2.0.0-preview/article-outline.md

@@ -0,0 +1,57 @@
+# Article Outline - ECC 2.0 Preview
+
+## Working Title
+
+How I Turned ECC Into an Operator System With Hermes
+
+## Core Argument
+
+Most people treat AI coding tools like isolated chat products.
+
+The leverage comes when you treat the harness, workflow surface, and operator stack as a system:
+
+- reusable skills
+- stable hooks
+- MCP-backed tools
+- cron/accountability loops
+- one operator shell tying the pieces together
+
+## Structure
+
+### 1. The Problem
+
+- too many tools
+- too much context switching
+- too many workflows stuck in personal muscle memory
+
+### 2. What ECC Already Solved
+
+- reusable skills
+- cross-harness portability
+- hook discipline
+- verification and security patterns
+
+### 3. Why Hermes Was the Missing Layer
+
+- chat + TUI + cron + workspace memory
+- business and content ops live next to engineering
+- terminal-native operator flow instead of app sprawl
+
+### 4. What Ships in the Public Preview
+
+- sanitized Hermes setup guide
+- generated workflow skills
+- release and distribution collateral
+- cross-harness 2.0 positioning
+
+### 5. What Is Still Private or Still Coming
+
+- secrets and auth
+- personal datasets
+- some operator-specific automation packs
+- deeper CRM/finance/Google Workspace integrations
+
+### 6. Closing Point
+
+The goal is not “use my exact stack.”
+The goal is to build an operator system that compounds.

docs/releases/2.0.0-preview/launch-checklist.md

@@ -0,0 +1,37 @@
+# ECC 2.0 Preview Launch Checklist
+
+## Repo
+
+- update public version surface
+- publish Hermes setup guide
+- verify release notes and launch assets are committed
+- leave private tokens, personal docs, and raw workspace exports out of repo
+
+## Content
+
+- post X thread from `x-thread.md`
+- post LinkedIn draft from `linkedin-post.md`
+- turn one of the short clips in `video-shorts.md` into a 30-60 second video
+- use `article-outline.md` to draft the longer writeup
+
+## Demo Asset Suggestions
+
+- terminal view of Hermes + ECC side by side
+- Drive playbook -> brief -> post workflow
+- cron or readiness artifact showing operator accountability
+- one short proof-of-work clip instead of a polished brand reel
+
+## Call To Action
+
+- repo link
+- Hermes setup doc link
+- one sentence on why this is preview and what comes next
+
+## Preview Messaging
+
+Use language like:
+
+- "public preview"
+- "sanitized operator stack"
+- "shipping the reusable surface first"
+- "private/local integrations land later"

docs/releases/2.0.0-preview/linkedin-post.md

@@ -0,0 +1,29 @@
+# LinkedIn Draft - ECC 2.0 Preview
+
+ECC 2.0 preview is live.
+
+This is the first public version of a setup I have been converging toward for a while: one operator stack for engineering, research, content, outreach, and business operations.
+
+The practical shift is that ECC is no longer framed as only a Claude Code plugin or config bundle.
+
+It is a cross-harness operating system for agentic work:
+
+- reusable skills instead of one-off prompts
+- hooks and workflow automation instead of manual checklists
+- MCP-backed access to research, docs, browser automation, finance, and distribution surfaces
+- a Hermes operator shell on top for chat, cron, accountability, and orchestration
+
+For the public preview I kept the repo honest.
+
+I did not dump a private workspace into GitHub. I shipped:
+
+- a sanitized Hermes setup guide
+- launch-ready release collateral
+- the reusable parts of the workflow surface
+- aligned versioning across the public repo
+
+If you are building with AI coding tools daily, the real leverage is not just prompting better.
+
+It is reducing surface area, consolidating workflows, and making your operator system measurable and repeatable.
+
+I will keep adding the remaining pieces incrementally, but this preview is enough to start from.

docs/releases/2.0.0-preview/release-notes.md

@@ -0,0 +1,51 @@
+# ECC 2.0 Preview Release Notes
+
+## Positioning
+
+ECC 2.0 preview turns the repo into a more explicit cross-harness operating system.
+
+Claude Code is still a core target. Codex, OpenCode, and Cursor remain first-class. Hermes now joins the public story as the operator shell that can sit on top of ECC.
+
+## What Changed
+
+- Public repo metadata now aligns with the 2.0 direction already visible in the plugin manifest and architecture docs.
+- Hermes setup is documented as a sanitized, reusable operator stack.
+- Hermes-generated skills are now easier to explain as part of ECC's reusable workflow layer.
+- Same-day launch collateral is included in-repo so the release can ship without rebuilding the messaging from scratch.
+
+## Why This Matters
+
+ECC is no longer just “Claude Code tips in a repo.”
+
+It is a reusable system for:
+
+- engineering execution
+- research and market intelligence
+- outbound and comms operations
+- content production and distribution
+- operator accountability through hooks, cron jobs, and workflow packs
+
+## Preview Boundaries
+
+This is a public preview, not the final form.
+
+What ships now:
+
+- cross-harness positioning
+- Hermes setup documentation
+- launch content pack
+- version alignment across root package surfaces
+
+What can land later:
+
+- richer sanitized Hermes templates
+- more public MCP presets
+- deeper CRM and Google Workspace playbooks
+- additional operator packs distilled from live usage
+
+## Suggested Upgrade Motion
+
+1. Update to the ECC 2.0 public surface.
+2. Read the [Hermes setup guide](../../HERMES-SETUP.md).
+3. Pick the workflows you want public first: content, research, outreach, or engineering.
+4. Use the launch pack in this folder to announce the release without re-drafting everything from scratch.

docs/releases/2.0.0-preview/video-shorts.md

@@ -0,0 +1,79 @@
+# Short-Form Video Scripts - ECC 2.0 Preview
+
+These are designed for 30-60 second clips. Record directly from the terminal and Hermes UI where possible.
+
+## Clip 1 - "I Replaced Five Apps With One Operator Stack"
+
+### Hook
+
+"I got tired of switching between coding tools, research tabs, notes, and outreach dashboards, so I collapsed it into one operator stack."
+
+### Beat Outline
+
+1. Show ECC repo and Hermes side by side.
+2. Explain: ECC holds the reusable skills, hooks, and MCP patterns.
+3. Explain: Hermes is the operator shell that runs the workflows.
+4. Flash examples:
+   - coding
+   - research
+   - content
+   - cron nudges
+5. Close with: "This is ECC 2.0 preview."
+
+### On-Screen Text
+
+- "one operator stack"
+- "skills + MCPs + automations"
+- "Hermes x ECC"
+
+## Clip 2 - "How I Turn Drive Playbooks Into Content"
+
+### Hook
+
+"This is how I turn raw operating docs into posts and videos without starting from a blank page."
+
+### Beat Outline
+
+1. Open the Ito playbooks folder.
+2. Show Hermes pulling the source material into a working brief.
+3. Show ECC release/content docs as the packaging layer.
+4. Show output targets:
+   - X thread
+   - LinkedIn post
+   - short clip script
+5. Close with: "One source, multiple outputs."
+
+### On-Screen Text
+
+- "Drive -> brief -> posts -> clips"
+- "no blank page"
+
+## Clip 3 - "Why Hermes Matters"
+
+### Hook
+
+"The point of Hermes is not another chat app. It is operator control."
+
+### Beat Outline
+
+1. Show a cron or readiness check artifact.
+2. Explain that Hermes can audit, remind, and route work.
+3. Show ECC skills and MCP-backed workflows behind the scenes.
+4. Explain why terminal-native matters:
+   - fewer tabs
+   - better repeatability
+   - faster execution
+5. Close with the preview framing.
+
+### On-Screen Text
+
+- "operator control"
+- "terminal-native"
+- "ECC 2.0 preview"
+
+## Recording Notes
+
+- Prefer live typing plus quick jump cuts over long screen recordings.
+- Keep each beat under 5 seconds.
+- Use captions aggressively.
+- End each clip with the repo URL or doc title on screen.

docs/releases/2.0.0-preview/x-thread.md

@@ -0,0 +1,59 @@
+# X Thread Draft - ECC 2.0 Preview
+
+1/ ECC 2.0 preview is live.
+
+This is the first public pass at the setup I actually want to run daily: one operator stack for coding, research, content, outreach, and business ops.
+
+2/ The shift is simple:
+
+ECC is no longer just a Claude Code config pack.
+It is a cross-harness operating system for agentic work.
+
+3/ Claude Code, Codex, Cursor, and OpenCode are still in the mix.
+
+Now Hermes joins the public story as the operator shell on top of ECC skills, MCPs, hooks, and workflow packs.
+
+4/ I wanted fewer surfaces, not more.
+
+Less “which app do I open?”
+More “one place where the system already knows the workflows.”
+
+5/ The preview ships a sanitized Hermes setup guide, not a raw private workspace dump.
+
+That means:
+- no secrets
+- no personal tokens
+- no fake polish
+- just the reusable system shape
+
+6/ I also added release collateral directly in the repo:
+- release notes
+- launch checklist
+- LinkedIn draft
+- short-form video scripts
+
+7/ Why?
+
+Because half the battle with agent systems is not building them.
+It is operationalizing them:
+- shipping content
+- tracking revenue
+- triaging comms
+- keeping research and execution in one loop
+
+8/ If you want the repo:
+read the Hermes setup doc first, then lift the parts you need.
+
+You do not need my exact stack.
+You need a system that compounds.
+
+9/ ECC 2.0 is still preview.
+
+The public docs ship now.
+The rest lands incrementally as the operator surface hardens.
+
+10/ Repo + docs:
+<repo-link>
+
+Hermes x ECC setup:
+<repo-link>/blob/main/docs/HERMES-SETUP.md