Guide · Agent skill
How to use the Lark Skill Maker agent skill (lark-skill-maker)
Updated · written with AI from the project's own documentation and checked against our catalogue data
Lark Skill Maker is an agent skill, a SKILL.md instruction file that teaches an AI agent how to do a specific job. This one teaches the agent to write new skills for lark-cli, the command-line tool for Lark/Feishu. It is aimed at developers and teams who want to turn repeated Lark API work into reusable, shareable recipes. After this guide you will know how to install the skill, ask for a new skill in plain language, and review what the agent produces.
Lark Skill Makerlarksuite/cli · MIT Download the skill Quick start
- 1Install lark-cli. Install the lark-cli command-line tool, since the skill requires it as a binary.
- 2Authenticate. Log in with lark-cli auth login so API calls can run against your Lark/Feishu account.
- 3Download and place the skill. Download the ZIP from this page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder, or upload it under Settings → Capabilities → Skills in the Claude apps.
- 4Describe the skill you need. Ask the agent in plain language for a skill that wraps one Lark API or chains several steps.
- 5Check parameters and scopes. Use lark-cli <service> --help and lark-cli schema to confirm endpoints, parameters and required permissions.
- 6Review and save the SKILL.md. Read the generated file, test read-only calls first, and only then save it under skills/lark-<name>/SKILL.md.
What does the lark-skill-maker skill make the agent do?
In this project, a skill is a SKILL.md file that tells an AI agent how to complete a task using CLI commands. The lark-skill-maker skill helps the agent write a new one for lark-cli, either wrapping a single Lark API call or orchestrating a multi-step workflow.
The agent follows a research process before writing: it checks which services and shortcuts lark-cli already provides, looks up parameter definitions, falls back to raw API calls when needed, and works out which permission scopes the workflow requires. The result is a SKILL.md draft built from a template.
- Wraps atomic Lark API operations into a reusable skill
- Orchestrates multi-step flows and documents how data passes between steps
- Lists the required scopes (permissions) for each operation
- Follows key principles such as clear trigger descriptions and confirming intent before write actions
Install the lark-skill-maker skill
Download the skill ZIP from this page. Then choose one of two options.
For Claude Code, unzip it into your user skills folder ~/.claude/skills/, or into a project's .claude/skills/ folder if you want the skill limited to one project.
In the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.
- Option A (personal): unzip into ~/.claude/skills/
- Option B (project only): unzip into your project's .claude/skills/
- Option C (Claude apps): Settings → Capabilities → Skills, then upload the ZIP
Set up lark-cli and log in
The skill declares lark-cli as a required binary, so it must be installed before the skill is useful. Any real API call also needs a Lark/Feishu account authenticated through lark-cli. The source shows the login command as lark-cli auth login; when a domain is needed, the template uses the form lark-cli auth login --domain <name>.
The skill also refers to two companion skills, lark-openapi-explorer and lark-shared. Keep them available alongside this one so the agent can follow those references.
- Install lark-cli (the skill requires it as a binary)
- Authenticate with lark-cli auth login
- Make sure lark-openapi-explorer and lark-shared are present
lark-cli auth loginTrigger the skill with natural requests
You do not need a special command. The skill's description tells the agent when to use it, so describe what you want in plain language. Phrases that mention creating a skill, wrapping a Lark API, or chaining several API calls into one workflow are the most likely to trigger it.
Be specific about the goal. Name the Lark service or resource, the action, and whether it is a single call or a sequence of steps.
- "Create a lark-cli skill that wraps the Lark meeting room search API."
- "Write a reusable skill that creates a Lark document and then adds it to a folder."
- "Package our weekly report workflow of several Lark API calls into a shareable skill."
Review the generated skill before you use it
The skill is documentation only. It does not call Lark itself, and it relies on the agent's research to pick the right APIs, parameters and scopes. Check each endpoint, parameter and permission the agent lists against the official Lark/Feishu documentation or against lark-cli's own help output before you share the skill.
Expect the output to follow the template: a frontmatter block with name, version, description and required binaries, then a commands section and a permissions table.
- Confirm each path and parameter, using lark-cli <service> --help or lark-cli schema
- Check that every listed scope matches what the workflow needs, no more
- Test read-only calls first before any write operation
lark-cli schema <service.resource.method>What people use it for
- Packaging a repeated Lark document or calendar task into a single reusable skill for a team
- Wrapping an unregistered Lark OpenAPI endpoint with lark-cli api so others can call it by following a recipe
- Documenting a multi-step workflow that passes an ID from one API call to the next, with the data flow spelled out
- Building an organisation-specific set of lark-cli skills that share one authentication setup
Frequently asked questions
Is the lark-skill-maker skill free to use?
The skill is published under the MIT licence, which is stated for this item. The skill itself performs no Lark actions. Using the generated skills still requires lark-cli and an authenticated Lark/Feishu account.
What do I need before installing lark-skill-maker?
You need the lark-cli command-line tool installed, since the skill declares it as a required binary. You also need a Lark/Feishu account authenticated with lark-cli auth login for any real API calls, plus the companion lark-openapi-explorer and lark-shared skills.
Where do I put the lark-skill-maker files?
Unzip the downloaded ZIP into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder to limit it to that project. In the Claude apps, upload the ZIP under Settings → Capabilities → Skills.
Does this skill run scripts or use the network?
No. The skill is a single SKILL.md file, it runs no scripts and does not use the network itself. Any network activity comes from the lark-cli commands the generated skills later run.
How is this different from lark-openapi-explorer?
Lark Skill Maker writes a new skill file for lark-cli. The companion lark-openapi-explorer is the tool the skill uses to research native OpenAPI endpoints in the official Lark/Feishu documentation when lark-cli has no registered command for what you need.
Why won't the generated skill work for me?
The most likely causes are that lark-cli is not installed, you have not run lark-cli auth login, or the account lacks the scope listed in the skill. Because the skill relies on the agent's research, also verify endpoint paths and parameters, since the skill does not check them.
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
Choose this skill if you are a developer or team building internal automations on Lark/Feishu and want an agent to draft reusable lark-cli recipes with documented scopes. Skip it if you only want to use Lark, or if you lack lark-cli and an authenticated account, since the skill cannot verify the API calls it writes.
Download the skill