ClawHub

Feishu/Lark Setup and Troubleshooting

v1.2.2

Set up and troubleshoot Feishu or Lark messaging integration with Hermes Agent, including connection checks, access control, and common failure modes.

⭐ 0· 103·0 current·0 all-time
byXuXu@xuxuclassmate

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for xuxuclassmate/feishu-setup-troubleshooting.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Feishu/Lark Setup and Troubleshooting" (xuxuclassmate/feishu-setup-troubleshooting) from ClawHub.
Skill page: https://clawhub.ai/xuxuclassmate/feishu-setup-troubleshooting
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: FEISHU_APP_ID, FEISHU_APP_SECRET, FEISHU_DOMAIN, FEISHU_CONNECTION_MODE, FEISHU_GROUP_POLICY, FEISHU_ALLOW_ALL_USERS, GATEWAY_ALLOW_ALL_USERS, FEISHU_ALLOWED_USERS, FEISHU_ENCRYPT_KEY, FEISHU_VERIFICATION_TOKEN
Required binaries: hermes
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install feishu-setup-troubleshooting

ClawHub CLI

Package manager switcher

npx clawhub@latest install feishu-setup-troubleshooting
Security Scan
Capability signals
Requires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name and description (Feishu/Lark setup & troubleshooting for Hermes Agent) match the declared requirements: the hermes CLI is required and the env vars are Feishu- and gateway-related (APP_ID, APP_SECRET, DOMAIN, connection/allowlist settings, encryption and verification tokens). These are proportionate to the stated purpose.
✓
Instruction Scope
SKILL.md contains operational troubleshooting steps limited to checking configuration, running hermes gateway status/logs/restart, and testing messages. It does not instruct reading unrelated system files, contacting arbitrary external endpoints, or exfiltrating data. It does recommend reviewing logs (which may contain sensitive data), but also warns not to share secrets.
✓
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so nothing is downloaded or written to disk by the skill itself.
✓
Credentials
The required environment variables are Feishu/Lark and gateway configuration items that a troubleshooting flow legitimately needs. The primary credential is the app secret, which is expected. The number of variables is large but appropriate for integration configuration.
✓
Persistence & Privilege
The skill is not always-enabled and does not request system-wide persistence or modify other skills. Model invocation is permitted (the platform default); while autonomous invocation increases blast radius in general, it is not combined with other red flags here.
Assessment
This skill appears coherent for Feishu/Lark troubleshooting with Hermes. Before installing, ensure the hermes CLI is trustworthy and available, store FEISHU_APP_SECRET and other tokens in a secure secret store (do not paste into public logs), and prefer testing in a development environment first. Limit allowed users (use allowlists) and run the gateway under a low-privilege account. When following log instructions, inspect and redact any secrets before sharing externally. If you do not want the skill to run autonomously with access to these credentials, avoid enabling it or restrict its use to manual invocation only.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

Binshermes
EnvFEISHU_APP_ID, FEISHU_APP_SECRET, FEISHU_DOMAIN, FEISHU_CONNECTION_MODE, FEISHU_GROUP_POLICY, FEISHU_ALLOW_ALL_USERS, GATEWAY_ALLOW_ALL_USERS, FEISHU_ALLOWED_USERS, FEISHU_ENCRYPT_KEY, FEISHU_VERIFICATION_TOKEN
Primary envFEISHU_APP_SECRET
devopsvk977zzp853e7ekkjd1662ktvgx85amv2feishuvk977zzp853e7ekkjd1662ktvgx85amv2integrationvk977zzp853e7ekkjd1662ktvgx85amv2larkvk977zzp853e7ekkjd1662ktvgx85amv2latestvk977zzp853e7ekkjd1662ktvgx85amv2messagingvk977zzp853e7ekkjd1662ktvgx85amv2setupvk977zzp853e7ekkjd1662ktvgx85amv2troubleshootingvk977zzp853e7ekkjd1662ktvgx85amv2
103downloads
0stars
5versions
Updated 6d ago
v1.2.2
MIT-0
XuXu@xuxuclassmate
devopsfeishuintegrationlarklatestmessagingsetuptroubleshooting
Download

Feishu or Lark Setup and Troubleshooting

When to use

  • A user wants to connect Hermes Agent to Feishu or Lark.
  • The bot is online but does not reply to messages.
  • You need to diagnose permissions, gateway state, or connection issues.

Prerequisites

  • Hermes Agent is installed and the hermes CLI is available.
  • A Feishu or Lark app exists with bot capability enabled.
  • The required App ID and App Secret are available.

Access-control reminder

Feishu access has two separate layers:

  • FEISHU_ALLOW_ALL_USERS
  • GATEWAY_ALLOW_ALL_USERS

If the gateway layer is still closed, Feishu users will be rejected even when the Feishu layer looks open.

Setup and troubleshooting flow

  1. Confirm configuration. Check that the required Feishu or Lark variables are present and that the domain and connection mode match the deployment.
  2. Confirm the gateway is running.
hermes gateway status
  1. Review recent logs.
hermes logs 2>&1 | grep -i feishu | tail -20
  1. Test message delivery. Send a direct message and look for an inbound message log followed by a model response.
  2. Restart after config changes.
hermes gateway restart

Common issues

  • Bot does not reply at all: the gateway is not running.
  • Unauthorized user in logs: the gateway-level allow rule is still blocking access.
  • Wrong region or domain: FEISHU_DOMAIN does not match the deployment.
  • Messages arrive but there is no answer: the model provider or API key behind Hermes is failing.

Security notes

  • Prefer an allowlist for production.
  • Never commit App Secret, encrypt keys, or verification tokens.
  • Keep the gateway running under a limited user account.
  • Review logs for sensitive output before sharing them externally.

Comments

Loading comments...