agentleFS
70asunflower70asunflower/70asunflower-skills/feishu-bot-config/SKILL.md

feishu-bot-config

Skill1 starsChanged 14 days agoMITView on GitHub

Manage Feishu (Lark) bot integrations with OpenClaw agents — add new bots, configure App ID/App Secret, set up routing, list configured bots, and troubleshoot connectivity. Use whenever the user mentions Feishu bots, wants to connect a Feishu app to an agent, configure channels or bindings, troubleshoot a bot not responding, or manage pairing.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the automated configuration script:

    line 12
  2. Distinctive:

    After the script completes, remind the user of the remaining manual steps:

    line 23
  3. Distinctive:

    Run the listing script to see all configured bots and their binding status:

    line 31
  4. Very specific:

    If a bot doesn't respond, check these in order — use list_feishu_bots.py first to quickly spot missing bindings:

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Feishu Bot Configuration Management

Workflow

Adding a New Feishu Bot

Run the automated configuration script:

scripts/add_feishu_bot.py <agent_name> <app_id> <app_secret>

The script handles three steps:

  1. Creates .env file with credentials in ~/.openclaw/workspace-<agent_name>/
  2. Adds the Feishu account to channels.feishu.accounts in ~/.openclaw/openclaw.json
  3. Adds a binding route to connect the account to the specified agent

After the script completes, remind the user of the remaining manual steps:

  1. Restart Gateway: openclaw gateway restart
  2. User starts a conversation with the bot in Feishu to get a pairing code
  3. Approve the pairing: openclaw pairing approve feishu <CODE>

Listing Configured Bots

Run the listing script to see all configured bots and their binding status:

scripts/list_feishu_bots.py

This reads ~/.openclaw/openclaw.json and shows each bot's App ID, default agent, and whether the binding route is present.

Troubleshooting

If a bot doesn't respond, check these in order — use list_feishu_bots.py first to quickly spot missing bindings:

SymptomLikely causeFix
Bot no responseMissing channels.feishu.accounts configAdd account with script or manually
Bot no responseMissing bindings routeAdd binding with script
Bot no responseGateway not restartedopenclaw gateway restart
Pairing requiredUser hasn't been approvedopenclaw pairing approve feishu <CODE>
Credential errorWrong App SecretCheck/fix .env file

For the full manual configuration checklist, see references/checklist.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.