ov-layers/skills/hermes-full/SKILL.md
Hermes agent with AI CLIs (Claude Code, Codex, Gemini), developer tools, DevOps tools, and ov. Use when working with the hermes-full metalayer or full-featured standalone hermes deployments.
npx skillsauth add overthinkos/overthink-plugins hermes-fullInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Metalayer composing Hermes AI agent with a complete tool suite for standalone deployment. No browser included — use with selkies-desktop via cross-container env_provides: BROWSER_CDP_URL for shared browser automation.
layers:
- hermes # AI agent with browser tools, MCP, LLM auto-config
- claude-code # Anthropic Claude Code CLI
- codex # OpenAI Codex CLI
- gemini # Google Gemini CLI
- dev-tools # bat, ripgrep, neovim, gh, direnv, fd-find, htop, etc.
- devops-tools # AWS CLI, Scaleway, kubectx, OpenTofu, wrangler, jq, rsync
- ov # Overthink CLI for in-container management
- tmux # Terminal multiplexer for persistent sessions
The hermes layer declares env_accepts: BROWSER_CDP_URL. When deployed alongside a selkies-desktop container, the chrome layer's env_provides injects BROWSER_CDP_URL=http://ov-selkies-desktop:9222 into the hermes quadlet via ov config --update-all. Hermes browser tools (browser_navigate, browser_click, browser_snapshot) then control the desktop Chrome across the container network.
Without a browser provider, hermes browser tools fall back to local headless mode (requires hermes-playwright layer) or are unavailable.
# image.yml
hermes:
base: fedora
layers:
- agent-forwarding
- hermes-full
- dbus
/ov-layers:hermes — Core Hermes agent (LLM providers, MCP, browser dispatch)/ov-layers:claude-code — Anthropic Claude Code CLI/ov-layers:codex — OpenAI Codex CLI/ov-layers:gemini — Google Gemini CLI/ov-layers:dev-tools — Developer CLI utilities/ov-layers:devops-tools — Cloud and infrastructure tools/ov-layers:ov — Overthink CLI binary/ov-layers:tmux — Terminal multiplexer for persistent sessions (ov tmux commands)/ov-layers:chrome — Provides BROWSER_CDP_URL (cross-container, from selkies-desktop)/ov-layers:chrome-devtools-mcp — Chrome DevTools MCP server (auto-discovered via mcp_provides, 29 tools)/ov-layers:jupyter-mcp — JupyterLab CRDT MCP server (auto-discovered via mcp_provides, 13 tools)/ov:mcp — host-side MCP client (ov test mcp ping|list-tools|call|...) to verify either of the above is alive and exposing the expected tool catalog before hermes tries to invoke them/ov-images:hermes — Standalone full-featured hermes image/ov-images:hermes-playwright — Hermes with local Playwright ChromiumUse when working with the hermes-full metalayer, full-featured standalone hermes deployments, or the composition of hermes with AI CLIs and developer tools.
/ov:layer — layer authoring reference (layer.yml schema, task verbs, service declarations)/ov:test — declarative testing (tests: block, ov image test, ov test)tools
Use when authoring or modifying a charly PLUGIN — a candy with a `plugin:` block that contributes Providers (verbs/kinds/deploy-targets/steps/builders/commands), its own CUE schema, builtin (compiled-in) or external (out-of-tree git repo). Covers the unified Provider model, the per-plugin CUE-schema contract (single source → Go params for dev + schema-over-Describe RPC for runtime), the SDK, and the loader.
tools
The CUE data-validation / configuration CLI (cue), pinned to v0.16.1. Use when working with the cue candy, installing the cue binary into a box or onto a target:local dev host, or running the offline schema-vendoring pipeline that feeds charly's egress validation.
tools
CUE EGRESS validation — validating (and, where it adds value, generating) the config files charly WRITES to a system BEFORE the bytes hit disk. MUST be invoked before working on charly/egress.go, the vendored schemas under candy/plugin-egress/egress-schemas/vendor/, the ValidateEgress / registerVendoredEgressKind path, the offline `task cue:vendor` pipeline, or adding an egress schema for any written artifact (cloud-init, k8s manifests, traefik routes, runtime config, install ledger, systemd/quadlet units, ssh_config, libvirt XML).
tools
Kubernetes cluster-probe declarative check verb — the `kube:` check verb (nodes, pods, ingress, storage class, addon health, apply/delete, and arbitrary resource GETs) served out-of-process by the candy/plugin-kube plugin (vendored client-go; no external kubectl required).