hermes3000-writing

# Hermes3000 Writing ## Overview Use Hermes3000 when the user wants a durable long-form writing project managed in the writing portal, not just a one-off draft in chat. Hermes3000 stores book structure, chapter content, consistency memory, timeline data, stats, and exports. For endpoint details, request shapes, and examples, read `references/api-workflow.md` before making live API calls. ## Secret Refs The bundled helper sends all live Hermes3000 calls through the HybridClaw gateway proxy, matching the Salesforce skill pattern. Login credentials are sent as `<secret:NAME>` placeholders; the gateway resolves them server-side, captures the returned Hermes3000 JWT into `HERMES3000_JWT`, and returns only a capture confirmation. The JWT does not enter the agent context. Never call Hermes3000 with `curl` or a raw `Authorization: Bearer ...` header. Use `node skills/hermes3000-writing/scripts/hermes3000.cjs ... run ...` for live calls so the gateway injects and captures secrets server-side. Run these helper commands exactly as documented. Do not add Node permission flags such as `--experimental-permission`, and do not rewrite `skills/...` paths to `/workspace/skills/...`; the helper needs runtime-provided gateway access for secret resolution. Cloud and chat/TUI users may not have a terminal. Only ask the user to set secrets with chat/TUI secret commands; do not ask them to run `node`, `curl`, or `hybridclaw` shell commands. If `HERMES3000_JWT` is missing or blocked, run `auth...