deploy-hermes-docker-agent
Deploy a randomized local Docker Hermes agent with Ollama Cloud and SearXNG.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Deploy a randomized local Docker Hermes agent with Ollama Cloud and SearXNG.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Set up a Microsoft Teams/Microsoft 365 Teams SDK bot that bridges Teams chat to a Nous Research Hermes Agent HTTP API.
Deploy OpenClaw gateway instances on Kubernetes with SearXNG as the web search provider. Use when the user wants to (1) Deploy a new OpenClaw instance, (2) Configure or verify SearXNG search integration, (3) Generate OpenClaw configuration files, (4) Set up K8s manifests for OpenClaw + SearXNG, or (5) Troubleshoot search provider connectivity in an OpenClaw deployment.
Manage and inspect Shrubnet's n8n automation server via the n8n Public API. Use when the user asks about n8n workflows, executions, credentials metadata, tags, users, webhook automation, debugging workflow runs, activating/deactivating workflows, creating/updating workflows, or checking the n8n server at n8n.cluster.shrubnet.com. Stores API credentials in the skill folder .env, never in SKILL.md.
Manage DNS records on Cloudflare via the Cloudflare MCP server or Cloudflare API v4. Use this skill whenever the user wants to view, create, update, or delete DNS records for a domain managed by Cloudflare, or when redirecting a domain on Cloudflare to a hosting provider (such as Netlify, DigitalOcean, Vercel, or any origin server). Triggers include any mention of "Cloudflare DNS", "Cloudflare", "CF DNS", "orange cloud", "proxied", "CNAME flattening", or general DNS management terms like "DNS records", "A record", "CNAME", "point domain to" when the domain is known to be on Cloudflare. Also triggers when another skill (like netlify-landing-page-deploy or digitalocean-management) needs DNS records updated on a Cloudflare-managed domain. This skill handles listing zones, reading existing records, creating/updating/deleting individual records, batch operations, and managing Cloudflare-specific features like proxy status (orange/grey cloud). It does NOT handle Cloudflare Workers, Pages, R2, WAF, or other non-DNS
Control the Raspberry Pi (LXDE) desktop via PyAutoGUI MCP. Implements a screenshot-reason-act-verify loop: take a screenshot, analyze what is visible, determine where to click or type, act, then immediately screenshot again to assess the result before proceeding. Use when the user asks to click, type, automate, or interact with any Linux GUI.
Control the Ubuntu/GNOME desktop on Wayland. Take screenshots, move mouse, click, and type. Uses ydotool for input simulation and GNOME Screencast service for screenshots (Wayland-compatible). Requires: ydotool, python3-dbus, wl-clipboard installed. IMPORTANT: Must run from the graphical session (SSH sessions need the wrapper).
| name | deploy-hermes-docker-agent |
| description | Deploy a randomized local Docker Hermes agent with Ollama Cloud and SearXNG. |
Use when Boss asks to deploy a new local Docker-hosted Hermes Agent like Birdie.
nousresearch/hermes-agent:latestollama-cloudglm-5.2:cloudhttps://ollama.com/v1searxnghttps://searxng.hoyack.aiAmerica/Chicagogateway run127.0.0.1:<host-port>->8642/tcp$HOME/.hermes-agents/<random-slug> mounted as /opt/dataOLLAMA_API_KEY or hidden terminal prompt. If a key was pasted in chat, recommend rotation after deployment is confirmed.8642 unless the user gives one.docker --version.Astra -> hermes-astra.8642.nousresearch/hermes-agent:latest.0700..env through a transient container using /opt/hermes/.venv/bin/python, not host-side YAML editing.docker run -d \
--name "$CONTAINER" \
--restart unless-stopped \
-v "$DATA_DIR:/opt/data" \
-p "127.0.0.1:$HOST_PORT:8642" \
nousresearch/hermes-agent:latest gateway run
docker ps --filter "name=$CONTAINER"
curl -sS --max-time 5 "http://127.0.0.1:$HOST_PORT/health"
docker exec "$CONTAINER" hermes status
docker exec "$CONTAINER" hermes doctor
Tell the user to open the TUI with:
docker exec -it <container-name> hermes --tui
Resume the latest TUI session with:
docker exec -it <container-name> hermes --tui --continue
Write these into /opt/data:
config.yaml with model.provider=ollama-cloud, model.default=glm-5.2:cloud, web.search_backend=searxng, display.interface=tui, and timezone=America/Chicago..env with OLLAMA_API_KEY, OLLAMA_BASE_URL, SEARXNG_URL, API_SERVER_ENABLED=true, API_SERVER_HOST=0.0.0.0, API_SERVER_PORT=8642, and a generated API_SERVER_KEY.SOUL.md naming the agent and describing the runtime.README-<SLUG>.md with start/stop/status/logs/TUI commands.Prefer scripts/deploy-hermes-docker-agent.sh when available. It implements the default deployment path and keeps the API key out of the process command line by reading it from OLLAMA_API_KEY or a hidden prompt.