lark-mail

Automate drafting, sending, replying, and forwarding emails in Lark.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/x0chaoren0s/agent-platform --skill lark-mail-x0chaoren0s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-mail
Source: https://github.com/x0chaoren0s/agent-platform/tree/main/skills/lark-mail
Command: npx skills add https://github.com/x0chaoren0s/agent-platform --skill lark-mail-x0chaoren0s

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive, CLI-based workflow for managing Feishu/Lark emails—drafts, sending, replying, forwarding, and threading—across mailboxes with attachments, signatures, and rules.

Core Features & Use Cases

  • Draft, send, reply, and forward emails using shortcuts such as +draft-create, +send, +reply, and +forward, with built-in safety and approvals.
  • Manage conversations and drafts across mailbox contexts, including attachments, inline images, and signatures, plus read receipts and recall-like capabilities.
  • Access native API schemas and shortcuts for automation, testing, or integration in team workflows.

Quick Start

Create a draft with +draft-create and then send with +send after user confirmation.

Frequently Asked Questions about lark-mail

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

FAQPage Schema
How do I automate sending and replying to Lark emails?

Automate Lark email workflows by using CLI shortcuts like +draft-create and +send to compose, reply, and forward messages across mailboxes. Built-in safety checks and user confirmations ensure secure end-to-end email processing.

Can I manage email drafts and attachments across different mailboxes in Lark?

Yes, you can manage drafts, attachments, and inline images across multiple Lark mailbox contexts. The Skill enables conversation tracking and draft evolution while observing access controls for secure mailbox management.

What is the best way to handle email threading and forwarding in Feishu?

Handle Feishu email threading and forwarding through specialized CLI commands like +reply and +forward. These commands manage thread evolution and message routing while applying necessary safety approvals before execution.

Do I need any specific dependencies to use this Lark mail workflow tool?

No external dependencies are required to use the Lark mail workflow tool. It operates independently using optional scripts and references directories to extend its native API schema capabilities for team automation.

Are there limitations when managing read receipts or recalling emails in Lark?

The tool supports read receipts and recall-like capabilities within Lark, but all actions are subject to built-in safety checks and access controls. These constraints ensure secure email automation across mailbox contexts.