Guide · Agent skill
How to use the Lark Minutes (Compatibility Entry) agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The lark-minutes skill is a small compatibility entry for an older skill name. It does not handle meeting work itself; it points the agent to the lark-meeting skill, which holds the actual routing and instructions. This guide explains what it does, how to install it, and when it is worth keeping.
Quick start
- 1Download the ZIP. Get the lark-minutes ZIP from this page and unzip it. It contains SKILL.md.
- 2Place the folder. Copy the lark-minutes folder into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder.
- 3Or upload in the Claude apps. Go to Settings → Capabilities → Skills and upload the ZIP.
- 4Install lark-meeting. Make sure the lark-meeting skill is installed and readable, since lark-minutes forwards to it.
- 5Confirm lark-cli is available. The skill metadata lists lark-cli as a required binary, so ensure it is installed.
- 6Invoke by name. Ask the agent to use lark-minutes explicitly so the shim routes the request to lark-meeting.
What is an agent skill, and what does lark-minutes do?
An agent skill is a folder containing a SKILL.md file. The file gives an AI agent instructions for a specific kind of task, and the agent reads it when a request matches the skill's description.
The lark-minutes skill is a compatibility shim. Its description says it applies only when the user or upstream configuration explicitly names lark-minutes, and that related requests are handled by the lark-meeting skill. Its body states it exists only to support the old name and does not process business requests directly.
- It only activates when lark-minutes is explicitly named.
- It tells the agent to fully read the lark-meeting SKILL.md and follow its routing and guidance.
- It contains no meeting instructions of its own.
Install the lark-minutes skill from the ZIP
Download the ZIP from this page and unzip it. The package contains one file, SKILL.md. Place the unzipped lark-minutes folder in one of the following locations.
For a personal install, put it in ~/.claude/skills/. For a single project, put it in that project's .claude/skills/ folder. Alternatively, upload the ZIP in the Claude apps under Settings → Capabilities → Skills.
- Personal: ~/.claude/skills/lark-minutes/
- Project: .claude/skills/lark-minutes/ inside your project
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP
~/.claude/skills/lark-minutes/SKILL.mdInstall the lark-meeting skill too
This shim does nothing useful alone. The source requires the lark-meeting skill, which must be installed and readable by the agent. Without it, a request routed through lark-minutes has nowhere to go.
The source also lists lark-cli as a required binary. Make sure the lark-cli command-line tool is available before you rely on Lark meeting workflows.
- lark-meeting skill: must be installed and readable.
- lark-cli: listed as a required binary in the skill metadata.
How to trigger it with natural requests
The skill only triggers when the request explicitly names lark-minutes, or when an upstream configuration does so. A general request about meeting notes will not reach this shim; it should reach lark-meeting directly.
If you maintain older configs that reference lark-minutes, those references will still resolve through this entry. Example phrasing: "Use the lark-minutes skill to handle this Lark meeting task."
- Explicit: "Use lark-minutes to pull up the notes from my Lark meeting."
- Configuration: an older config or upstream setting that names lark-minutes.
- Not triggered: a plain request for meeting notes that does not name the skill.
Migrate from lark-minutes to lark-meeting
If you are updating your setup, the cleaner path is to reference lark-meeting directly. The shim keeps existing references working while you migrate.
Because this entry only forwards requests, any behaviour, permissions and risks come from the lark-meeting skill. Review that skill before trusting the setup.
- Search your configs for the lark-minutes name.
- Replace references with lark-meeting where you can.
- Keep lark-minutes only where older references still need it.
Safety notes: scripts and network
According to the source, this skill runs no scripts and uses no network access on its own. Its only action is to read the lark-meeting SKILL.md file and follow it.
Because of that forwarding, the real risk surface sits in lark-meeting. Its behaviour, any scripts it runs and any network calls it makes are outside what this file describes, so check them there.
- Runs scripts: no (per the skill metadata).
- Uses network: no (per the skill metadata).
- The forwarded lark-meeting skill determines actual behaviour and risk.
What people use it for
- Keeping an older automation or config that names lark-minutes working after a rename.
- Migrating a team's references from lark-minutes to lark-meeting gradually.
- Testing whether an older config still resolves correctly before removing the old name.
Frequently asked questions
What is the lark-minutes skill?
It is a compatibility entry for an older skill name. It only activates when lark-minutes is explicitly named and then tells the agent to follow the lark-meeting skill.
Does lark-minutes do meeting transcription or notes by itself?
No. The source says it does not handle business requests directly and contains no meeting instructions of its own. The work is done by lark-meeting.
What do I need to install before using lark-minutes?
You need the lark-meeting skill installed and readable, and the lark-cli command-line tool, which the metadata lists as a required binary.
Where do I put the lark-minutes skill files?
Place the folder in ~/.claude/skills/ for personal use, or in a project's .claude/skills/ folder. You can also upload the ZIP under Settings → Capabilities → Skills in the Claude apps.
Is lark-minutes free or what is its licence?
The item is listed under the MIT licence. This page does not state pricing, so check the source repository for any other terms.
Should I use lark-minutes or lark-meeting for a new setup?
Use lark-meeting directly for new setups. Keep lark-minutes only if older configs still reference that name.
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-minutes only if older configurations or upstream settings still reference that name and you want them to keep working while you migrate. If you need a standalone meeting-minutes tool, this is not it, and you should install and review lark-meeting directly.
Download the skill