Skip to content

Guide · Agent skill

How to use the Lark Suite Router agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The Lark Suite Router is an agent skill for Feishu/Lark, the workplace suite from ByteDance also sold as Lark. It acts as a single entry point: when you ask for something that involves Lark products, the agent picks the matching Lark sub-capability and follows that sub-capability's guide. This page explains what the skill does, how to install it, how to trigger it, and what you need before it can do anything useful.

Lark Suite Routerlarksuite/cli · MIT

Quick start

  1. 1Get the ZIP. Download the lark-suite ZIP from this page.
  2. 2Install lark-cli. Install the lark-cli command-line tool, which the skill requires.
  3. 3Set up Lark access. Make sure you have a Lark or Feishu account and the authorisation lark-cli and lark-shared require.
  4. 4Unzip the skill. Unzip into ~/.claude/skills/ for personal use or .claude/skills/ in a project.
  5. 5Make a request. Describe a Lark task in plain language, naming the Lark product involved.
  6. 6Follow the sub-guide. The agent reads the matching references/<name>/GUIDE.md and completes the task, asking you for any missing details.

What is an agent skill and what does lark-suite do?

An agent skill is a folder with a SKILL.md file that tells an AI agent when and how to handle a certain kind of task. The agent reads the skill's instructions when a request matches its description.

lark-suite is a router, not a full toolkit. Its SKILL.md holds a routing list of Lark capabilities. For a request, the agent chooses one or more matching sub-capabilities, then reads the guide at references/<name>/GUIDE.md and follows it. The detailed Lark commands live in those sub-guides, not in this file.

  • Routes Lark requests from one entry point instead of many separate skills.
  • Chains capabilities in order when a task needs more than one, for example looking up a contact with lark-contact and then messaging them with lark-im.
  • Defers authentication, tenant, identity, permission and general troubleshooting to the lark-shared guide.

How do you install the lark-suite skill?

Download the lark-suite ZIP from this page. Then install it using one of the two methods below.

For Claude Code, unzip the file into your personal skills folder ~/.claude/skills/, or into a project-level .claude/skills/ folder inside your project.

In the Claude apps, you can upload the ZIP under Settings → Capabilities → Skills instead.

  • Personal install: unzip into ~/.claude/skills/
  • Project install: unzip into .claude/skills/ in your project folder
  • Claude apps: Settings → Capabilities → Skills, then upload the ZIP

What do you need before it works?

The skill declares lark-cli as a required command-line tool. Install and set up lark-cli first, because the routed sub-guides depend on it.

You also need a Lark or Feishu account, plus the authorisation and credentials that lark-cli and the lark-shared guide require. Without Lark access the routed tasks cannot run.

  • lark-cli command-line tool (declared as a required binary)
  • A Lark/Feishu account
  • Authorisation and credentials required by lark-cli and the lark-shared guide

How do you trigger the skill with a natural request?

You do not need a special command. Describe the Lark task in plain language and mention the Lark product involved. The skill's description covers requests that touch Feishu/Lark business areas.

If you don't yet have a link, ID or sheet name, you can still ask. The agent selects the capability first, and the sub-capability then asks for the missing details.

  • Ask about a Lark product by name, for example a message, contact or document task.
  • Combine steps in one request when the work spans products, for example: find a colleague in Lark contacts and send them a message.
  • Leave out IDs or links at first; the sub-guide will ask for what it needs.

What are some example requests?

The routing list in the file is filled in at publication time, so the exact list of sub-capabilities depends on the version you install. The examples below show the pattern of requests the router is built for.

  • Look up a colleague in Lark contacts, then send them a message.
  • Work with Feishu/Lark resources that appear on doubao.com subdomains.
  • Perform a multi-step Lark task where each step is handled by a specific sub-capability.

What are the safety notes?

This skill runs scripts and uses the network. Its tasks go through lark-cli and your Lark account, so the actions it takes have real effects in your workspace.

The file tells the agent to use this entry for Lark resources on doubao.com subdomains instead of falling back to generic web fetching. It also tells the agent not to guess commands or parameters from this file alone, and to read the relevant sub-guide first.

Only the SKILL.md file was reviewed. The sub-guides it points to are not included, so their actual behaviour cannot be verified from this page. Review them yourself before granting access to sensitive Lark data.

  • Runs scripts and uses the network.
  • Actions run through lark-cli under your Lark credentials.
  • Review the referenced GUIDE.md files before relying on them with sensitive data.

Tips for getting good results

Be specific about the Lark product and the outcome you want. The router picks capabilities from the request, so a clear goal helps it choose correctly.

If a request does not match any listed capability, the skill is designed to say so rather than guess.

  • Name the product and the action in the same sentence.
  • Provide IDs or links when you have them, but do not hold back a request for them.
  • Check that lark-cli is installed and authorised before you start.

What people use it for

  • Look up a Lark contact and send them a message in one request.
  • Handle a multi-step Lark workflow where each step uses a different sub-capability.
  • Work with Feishu/Lark resources linked from doubao.com subdomains without generic web fetching.

Frequently asked questions

How do I install the lark-suite skill?

Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use or into .claude/skills/ in a project. In the Claude apps you can instead upload the ZIP under Settings → Capabilities → Skills.

What do I need to use the lark-suite skill?

You need the lark-cli command-line tool, a Lark or Feishu account, and the authorisation and credentials that lark-cli and the lark-shared guide require. The routed tasks cannot run without Lark access.

Is the lark-suite skill free?

The source files reviewed do not state pricing or licence terms beyond the MIT licence listed for the item. Check the repository for the full licence text.

Does lark-suite contain the Lark commands itself?

No. It only routes requests. The detailed steps are in the sub-guides at references/<name>/GUIDE.md, which were not included in the files reviewed.

Why does the skill not work on its own?

It only holds a routing list. Without lark-cli, a Lark account and the required credentials, the sub-capabilities it routes to cannot perform Lark actions.

How is this different from other Lark tools or alternatives?

This skill is a single entry point that selects a Lark sub-capability per request. If you need a fixed, standalone workflow for one Lark product, a dedicated skill or the Lark tooling directly may suit you better. The source does not compare it with other options.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use lark-suite if your team already works in Feishu/Lark and you want an agent to handle several Lark products from one entry point. Pick something else if you have no Lark accounts, or if you need to verify exact behaviour, since the sub-guides that do the work were not included in the files reviewed.

Download the skill

Find exactly what
you're looking for