Lark CLI Skill: Messenger — Chat & Messages

What it is

The Lark CLI Messenger skill provides instant messaging capabilities for AI coding agents through the Lark/Feishu platform. It enables sending and replying to messages, managing group chats, searching chat history, and handling media uploads and downloads, all from the command line.

This skill is designed for developers and teams using Lark/Feishu who want their AI agents to communicate through the platform without switching to the Lark app.

How it saves time or tokens

Without this skill, interacting with Lark messaging requires the web app or mobile app, breaking your flow during AI-assisted development. The CLI skill lets your AI agent send status updates, ask questions in group chats, or search for past conversations without leaving the terminal. This is particularly useful for automated workflows where an agent needs to notify a team channel about build results or deployment status.

How to use

1. Install the Lark CLI and the Messenger skill:

npm install -g @larksuite/cli
npx skills add larksuite/cli -y -g

1. Configure authentication (one-time setup):

lark-cli config init
lark-cli auth login --recommend

1. Send a message to a chat:

lark-cli messenger send --chat-id oc_xxxxx --text 'Build completed successfully'

Example

Common Messenger skill commands:

# Send a text message
lark-cli messenger send --chat-id oc_xxxxx --text 'Deployment to staging is complete'

# Reply to a specific message
lark-cli messenger reply --message-id om_xxxxx --text 'Acknowledged, reviewing now'

# Search chat history
lark-cli messenger search --chat-id oc_xxxxx --query 'API endpoint'

# List group chats
lark-cli messenger list-chats

# Upload a file to a chat
lark-cli messenger upload --chat-id oc_xxxxx --file ./report.pdf

Related on TokRepo

• Automation tools — Browse tools for automating communication workflows
• AI tools for task management — Explore productivity and task management tools

Common pitfalls

• Not completing the lark-cli auth login step before trying to send messages. Without authentication, all API calls will fail with permission errors.
• Using the wrong chat ID format. Lark chat IDs start with oc_ for group chats. Use lark-cli messenger list-chats to find the correct ID.
• Sending too many messages in rapid succession. Lark has API rate limits. Add delays between batch message operations to avoid being throttled.
• Starting with an overly complex configuration instead of defaults. Begin with the minimal setup, verify it works, then customize incrementally. This approach catches configuration errors early and keeps troubleshooting straightforward.