Menu
Configure WhatsApp and Telegram messaging platforms on Hermes Agent
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
🧠 ontology-clawra v5.1 - Local Ontology Reasoning & Learning Engine **USE THIS SKILL WHENEVER** you need structured reasoning, knowledge graph management, logical inference, or learning from interactions. This is your go-to tool for: - Building and querying ontology knowledge graphs (concepts, entities, relationships) - Performing confidence-based reasoning with evidence tracking - Recording insights and patterns from completed tasks - Local memory search and knowledge retrieval **Key Use Cases:** - Before making complex decisions: "Let me use ontology-clawra to reason about this" - After completing tasks: "Record this learning to ontology-clawra" - Building domain expertise: "Create concepts for [domain] in ontology-clawra" - Analyzing patterns: "Query ontology-clawra for similar past cases" **Core Capabilities:** ✅ Local ontology storage in `~/.openclaw/skills/ontology-clawra/memory/` ✅ Confidence calculation (CONFIRMED/ASSUMED/SPECULATIVE) ✅ Learning from user confirmations ✅ Local memory search (no ne
Complete guide to using and extending Hermes Agent — CLI usage, setup, configuration, spawning additional agents, gateway platforms, skills, voice, tools, profiles, and a concise contributor reference. Load this skill when helping users configure Hermes, troubleshoot issues, spawn agent instances, or make code contributions.
Git push to HTTPS remote using token authentication — avoids SSH setup, works in CI/automated environments.
从 GitHub 历史中彻底清除敏感文件的完整流程 — 使用 git filter-repo + force push，适用于清理意外提交的个人文件、工作文件等
清理 GitHub 历史和 ClawHub 中意外泄露的个人/工作文件
Configure Telegram bot messaging channel for Hermes Agent, especially useful when behind Chinese firewall with SOCKS proxy
Baseado na classificação ocupacional SOC
| name | hermes-messaging-setup |
| description | Configure WhatsApp and Telegram messaging platforms on Hermes Agent |
Hermes Agent uses TWO separate config systems:
~/.hermes/config.yaml — general agent config~/.hermes/.env — messaging platforms, API keys, credentialsMessaging platforms (WhatsApp, Telegram, Discord, etc.) MUST be configured via .env, NOT config.yaml. Use hermes config set command, never edit .env directly.
WHATSAPP_MODE=bot
WHATSAPP_ALLOWED_USERS=13920378337 # International format, no + sign
Channel directory built: 0 target(s) = no active sessions yethermes whatsapp to re-pair if session was invalidated/newbot, follow prompts123456789:ABCdef...)hermes config set TELEGRAM_BOT_TOKEN "123456789:ABCdef..."
hermes config set TELEGRAM_ALLOWED_USERS "123456789" # Your Telegram user ID, NOT phone number
hermes gateway restart
Check logs: tail -20 ~/.hermes/logs/gateway.log
Should see: ✓ telegram connected
If Telegram fails with httpx.ConnectError or NetworkError:
networksetup -getsocksfirewallproxy Wi-Fi
launchctl setenv HTTP_PROXY socks5://127.0.0.1:7897
launchctl setenv HTTPS_PROXY socks5://127.0.0.1:7897
uv pip install httpx[socks] --python ~/.hermes/hermes-agent/venv/bin/python
hermes gateway restart
Note: Common proxy port is 7890 (Clash) or 7897 (ClashX), not 1080.
hermes config set approvals.mode autohermes gateway restart after config changeshermes gateway status # Check gateway and platform status
tail -20 ~/.hermes/logs/gateway.log # View recent logs