hermes-config

Use when you have a HARD, open-ended, high-stakes problem worth throwing multiple AI models at and pulling the best solution out — architecture decisions, strategy design, thorny debugging, research synthesis, "what am I missing", tool/system design. This is the SOLVE counterpart to multi-review (which critiques an existing artifact). It fans the problem out to a role-differentiated panel of model families (proposer layer), then the caller acts as aggregator and builds a NEW best-of-breed answer via a component ledger — not an average, not a cut-and-paste splice. Also encodes WHEN NOT to use a panel (most problems), routing to a single strong model or the commodity openrouter/fusion instead. Accumulates a persistent model-task-fit knowledge base so future runs pick the right models for the right roles.

Use to govern your own autonomy, deciding when to act on your own versus ask for approval, and earning more freedom over time the way a new employee earns trust through training and repetition. Group your capabilities into skill buckets, classify every action as a reversible (two-way) or irreversible (one-way) door, hold a trust level per bucket (L1 supervised, L2 guardrailed, L3 autonomous), and keep an honest markdown ledger of your decisions that you read back to promote or demote yourself. Load when setting up your autonomy rules or when a consequential act-vs-ask decision comes up.

On-demand real-time web and X (Twitter) search via xAI's Grok. Reach for this when the user explicitly wants Grok to search, or asks for real-time / breaking / X-Twitter-native results that a general web search misses. Not the default web search — a named tool you invoke deliberately.

Use when a Hermes MEMORY.md or USER.md file is too large, bloated, stale, or over the recommended cap and you need to reduce prompt footprint without losing important facts. Applies a lossless memory diet: compress, relocate to SOUL.md/USER.md/AGENTS.md/context files, offload long-tail facts to the memory provider, convert reusable procedures into skills, then drop only stale or duplicate material. Includes dry-run, diff, and review gates before any write.

Use when creating, importing, formatting, editing, exporting, or quality-checking Google Docs from agent-generated markdown or local files.

Use when creating, populating, formatting, importing, exporting, or quality-checking Google Sheets from CSV, JSON arrays, or computed tabular data.

Use when creating, importing, exporting, or quality-checking Google Slides decks via markdown-to-PPTX conversion and Drive import.

Use when adding, removing, password-protecting, or troubleshooting a mini-app served by the Hermes app-router (Caddy + PM2 + an Express auth sidecar + Tailscale Serve/Funnel) on a host. Covers install, the Caddy route pattern, the auth sidecar conventions, exposing Hermes dashboards behind a password, the web_dist build step, the HTTPS Secure-cookie requirement, and the recurring pitfalls (Tailscale serve resets, the PM2 $HOME trap, funnel-eligible ports, strip-prefix requirements).

Use when the user wants to know what real people are actually saying about a topic right now, not the SEO/editorial version. Pulls recent posts and engagement from Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, ranks by engagement and recency with a deterministic scorer, and writes one synthesized brief. Triggers: "what are people saying about X", "what's the vibe/sentiment on X", "X vs Y what does the community think", "how are people using X", "is X worth it", "latest on X", "take the pulse on X", "/mob-check", "what's the mob saying about X".

Use when operating, configuring, migrating to, or auditing OmniRoute — the self-hosted multi-provider LLM router that fronts Claude, OpenAI/Codex, Gemini, OpenRouter, and local models behind one OpenAI-compatible (and Anthropic Messages-compatible) endpoint. Covers pointing a Hermes agent at OmniRoute, importing OAuth/api-key provider credentials via the encrypt-on-write HTTP API (no re-login), the decisive refresh-token liveness checks, end-to-end verification that proves an imported credential actually works, and the provider-pool / priority model. Also use when diagnosing an agent that reports a provider-flavored error (401/402/429/billing) that is really a router fallback step, or answering "which provider/model served this request?" — the answer is in the router's call logs, not the agent's self-report.

Use when a pull request has feedback from code-review bots (Cursor Bugbot, Codex, Claude Code Review, Greptile, CodeRabbit) or humans and you need to triage it, fix what is valid, push back on what is wrong, react and reply to every comment, and drive the PR to a clean, mergeable state. Trigger phrases: "address the PR comments", "handle the bot feedback", "get the review comments addressed".

File a report or piece of feedback from any Hermes platform session. Load this skill when the user says "/report", "file a bug", "report a bug", "something's broken", "something's wrong", "that's weird", "this is wrong", "this isn't working", "log this issue", or any other signal that they want to capture a problem for triage. Works on Telegram, Discord, Slack, and the CLI — the closed loop (a notification back to this chat when the issue is resolved) is wired automatically for gateway sessions.

Use when reviewing almost any meaningful artifact, decision, action, plan, code change, prompt, skill, research summary, outbound message, or public-facing content. Runs a small panel of diverse review lenses across model families when available, synthesizes findings into fix/ask/defer/wontfix decisions, and iterates until the result is ready.

Restore context from prior sessions, memories, and transcripts. Run /recall after /new to pick up where you left off, and also use when a bare-pronoun follow-up like "ship it", "do it", or "send that" likely points at a prior-session artifact. Designed to never dead-end — if one source has nothing, keep searching others until you have a useful picture.

One-time bridge for fleet members migrating from OpenClaw to Hermes. Locates the OpenClaw transcript for the current Telegram topic, reads it, and hands the user a context briefing so the conversation can continue without losing its thread. Run once per topic after a migration; future recalls use /recall.

Detect broken Hermes cron jobs and escalate to a remediation sub-agent. Triage cheap, fix expensive.

Nightly sweep of recently-merged PRs to address unhandled review comments via a Claude Code sub-agent.