lark-note

Routes legacy lark-note requests to the lark-meeting skill for Lark meeting operations.

16.9k|1.4k|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/larksuite/cli --skill lark-note
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-note
Source: https://github.com/larksuite/cli/tree/main/skills/lark-note
Command: npx skills add https://github.com/larksuite/cli --skill lark-note

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Older configurations and user habits may still reference the legacy lark-note skill name, which no longer handles business logic directly. This Skill preserves backward compatibility by transparently forwarding all such requests to the lark-meeting skill, so existing setups keep working without reconfiguration.

Core Features & Use Cases

  • Legacy Name Compatibility: Accepts invocations under the old lark-note name without breaking existing workflows.
  • Unified Request Routing: Delegates all note and meeting-related requests to the lark-meeting skill's routing and action guidelines.
  • Use Case: A user's AI agent configuration still specifies lark-note for meeting notes. When triggered, this Skill loads the lark-meeting instructions and processes the request through the maintained meeting workflow.

Quick Start

Ask the agent to handle your Lark meeting notes request, and it will route the task through the lark-meeting skill automatically.

Frequently Asked Questions about lark-note

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What does the lark-note skill do in lark-cli?

The lark-note skill is a compatibility entry point only. It does not handle business logic itself and instead forwards all requests to the lark-meeting skill, whose routing and action guidelines are loaded and executed.

How do I manage Lark meeting notes with lark-cli?

Use the lark-meeting skill, which handles all meeting and note-related requests. If your setup references the older lark-note name, requests are automatically routed to lark-meeting without any changes needed.

Is lark-note deprecated in favor of lark-meeting?

Yes. lark-note exists solely for backward compatibility with older configurations. All actual functionality lives in the lark-meeting skill, which should be used directly for new setups.

What dependencies does the lark-note skill require?

It requires the lark-cli binary and the lark-meeting skill to be installed. Without lark-meeting present, the compatibility routing cannot load the required instructions and requests will fail.

When should I not use the lark-note skill?

Do not use it for new configurations or direct meeting operations. It should only activate when a user or upstream configuration explicitly specifies lark-note; otherwise invoke lark-meeting directly.