菜单
Debug Hermes gateway when Feishu/Lark credentials appear configured but the bot does not reply. Covers stale launchd env, platform-not-enabled states, websocket startup failure, and duplicate local gateway conflicts.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Undermybelt/hermes-skills --skill herm-feis-gate-dbgg命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when retiring old logic, collapsing duplicate owners, removing fallbacks, or touching schema, persistence, or source-of-truth boundaries while deciding whether to delete old paths, retain compatibility, or stop for confirmation.
Use when defining new features, product behavior, UI/component design, architecture choices, contract changes, or ambiguous medium/high-complexity work before implementation.
Use when the user asks for caveman mode, fewer tokens, brief responses, compressed communication, or otherwise explicitly requests a much shorter answer.
基于 SOC 职业分类
正在显示 SKILL.md
| name | herm-feis-gate-dbgg |
| description | Debug Hermes gateway when Feishu/Lark credentials appear configured but the bot does not reply. Covers stale launchd env, platform-not-enabled states, websocket startup failure, and duplicate local gateway conflicts. |
用时机：
hermes gateway status 显示服务在跑，仍怀疑飞书未接入先判定故障层：
app_idcd ~/.hermes/hermes-agent
. venv/bin/activate
python - <<'PY'
import os
from pathlib import Path
from hermes_cli.env_loader import load_hermes_dotenv
from hermes_constants import get_hermes_home
load_hermes_dotenv(hermes_home=get_hermes_home(), project_env=Path('~/.hermes/hermes-agent/.env').expanduser())
for k in ['FEISHU_APP_ID','FEISHU_APP_SECRET','FEISHU_DOMAIN','FEISHU_CONNECTION_MODE']:
v=os.getenv(k,'')
if 'SECRET' in k and v:
v=v[:4]+'***'+v[-4:]
print(k, bool(os.getenv(k)), v)
PY
hermes gateway status
ps -p <PID> -o pid=,ppid=,etime=,command=
grep -n "Feishu\|No messaging platforms enabled\|failed to connect any configured messaging platform" ~/.hermes/logs/gateway.log | tail -n 50
grep -n "Feishu\|No messaging platforms enabled\|failed to connect any configured messaging platform" ~/.hermes/logs/gateway.error.log | tail -n 50
No messaging platforms enabled.则结论优先为：当前常驻 gateway 进程启动时未载入 Feishu 配置；常见于配置后未重启、launchd 旧进程仍在跑。
[Feishu] FEISHU_APP_ID or FEISHU_APP_SECRET not set → env 未被进程读到[Feishu] lark-oapi not installed → 缺依赖Unsupported FEISHU_CONNECTION_MODE → 模式值错，只支持 websocket / webhookAnother local Hermes gateway is already using this Feishu app_id → 本机另一实例占锁Gateway failed to connect any configured messaging platform: → 平台启用但连接失败cd ~/.hermes/hermes-agent
. venv/bin/activate
hermes gateway restart
tail -f ~/.hermes/logs/gateway.log
应看到近似：
[Feishu] Connected in websocket modeGateway running with 1 platform(s)~/.hermes/hermes-agent/gateway/config.py
FEISHU_APP_ID + FEISHU_APP_SECRET~/.hermes/hermes-agent/gateway/platforms/feishu.py
connect() 内含依赖、凭据、连接模式、app_id 锁检查~/.hermes/hermes-agent/gateway/run.py
connected_count == 0 且 enabled_platform_count == 0，会写：No messaging platforms enabled.若同时满足：
FEISHU_APP_ID/SECRET 为真hermes gateway status 显示服务 loaded/runningNo messaging platforms enabled.则不要先怀疑用户消息格式；先判为“当前 launchd/gateway 进程未载入新 Feishu 配置”，重启 gateway 优先。
hermes gateway status，不看 gateway.error.logpython -m gateway.run，却被已有 PID 挡住，误判为 Feishu 故障