中文版 | English

lark-workflow

15 cross-domain workflow skills for Lark/Feishu CLI — orchestrate multiple business domains into powerful automated workflows.

While lark-cli provides 18 atomic skills for individual domains (Calendar, IM, Docs, Tasks, etc.), lark-workflow combines them into multi-step, cross-domain workflows that solve real-world productivity scenarios.

Quick Start

1. Install

Option A: via npx (GitHub source)

# Install lark-cli (if not already installed)
npm install -g @larksuite/cli

# Install official lark-cli skills (required dependency)
npx skills add larksuite/cli -y -g

# Install lark-workflow skills
npx skills add woodfantasy/lark-workflow -y -g

Option B: via OpenClaw (ClawHub)

openclaw install lark-workflow

2. Authenticate

# Recommended: authorize all commonly used domains at once
lark-cli auth login --recommend

3. Use

Simply tell your AI Agent what you need in natural language:

💬 "Give me today's briefing"           → daily-briefing
💬 "Write my weekly report"             → weekly-report
💬 "Extract action items from meeting"  → action-extractor
💬 "Summarize this document"            → doc-summarizer
💬 "What does the wiki say about X?"    → knowledge-qa
💬 "Prioritize my tasks for today"      → task-prioritizer
💬 "Schedule a meeting with X and Y"    → smart-scheduler
💬 "Where's my approval at?"            → approval-accelerator
💬 "Analyze this Bitable"               → base-analytics
💬 "New hire X is joining"              → onboarding
💬 "Generate docs from template"        → doc-template-engine
💬 "How efficient are my meetings?"     → meeting-efficiency
💬 "Who has bandwidth on the team?"     → workload-balancer
💬 "Audit the wiki for stale docs"      → wiki-auditor
💬 "Optimize my calendar"               → calendar-optimizer

The AI Agent reads the corresponding SKILL.md, understands the workflow, and executes the right lark-cli commands automatically.

Skills

🔄 Personal Productivity

🤝 Team Collaboration

📊 Data & Analytics

📚 Knowledge Management

How It Works

These skills are SKILL.md-based workflow definitions. Each SKILL.md file teaches an AI Agent how to orchestrate multiple lark-cli commands in a structured, step-by-step manner.

┌─────────────────────────────────────────────────────────────────────┐
│                          AI Agent                                    │
│     You say: "Give me today's briefing"                             │
│     Agent reads: daily-briefing/SKILL.md                            │
│     Agent executes: calendar → task → mail → approval → AI summary  │
└──────────┬──────────────────────────────────────────────────────────┘
           │
           ▼
┌─────────────────────────────────────────────────────────────────────┐
│                    lark-workflow Skills (15)                          │
│                                                                      │
│  Personal          Team             Analytics       Knowledge        │
│  ┌────────────┐  ┌──────────────┐  ┌────────────┐  ┌────────────┐  │
│  │briefing    │  │scheduler     │  │base-analyt.│  │doc-summary │  │
│  │weekly-rpt  │  │action-extr.  │  │meeting-eff.│  │knowledge-qa│  │
│  │task-prior. │  │onboarding    │  │doc-template│  │wiki-auditor│  │
│  │cal-optimiz.│  │workload-bal. │  └────────────┘  └────────────┘  │
│  └────────────┘  │approval-acc. │                                    │
│                  └──────────────┘                                    │
└──────────┬──────────────────────────────────────────────────────────┘
           │
           ▼
┌─────────────────────────────────────────────────────────────────────┐
│                  lark-cli Atomic Skills (18)                          │
│  calendar · task · mail · approval · im · vc · docs · drive         │
│  contact · minutes · base · sheets · wiki · event · whiteboard      │
└─────────────────────────────────────────────────────────────────────┘

What makes a SKILL.md?

Each skill follows the lark-skill-maker standard:

• YAML frontmatter — name, version, description, dependencies
• Trigger phrases — natural language patterns that activate the skill
• Workflow steps — Step 1 → 2 → 3... with exact CLI commands
• Output template — structured Markdown format for consistent results
• Permission table — required OAuth scopes per command
• Error handling — graceful degradation when a domain is unavailable

Authentication Reference

Each skill lists required scopes in its SKILL.md. Here's a quick reference:

Tip: Use lark-cli auth login --recommend to authorize the most commonly used scopes in one step.

Least-privilege alternative: If you only use a subset of skills, authorize only the domains you need — each row above shows the minimum scopes for that skill.

Security & Privacy

• No secrets stored — lark-workflow is instruction-only (SKILL.md files). It never reads, stores, or transmits credentials. Authentication is handled entirely by lark-cli auth, which stores tokens in the system keychain.
• No code execution — Installation adds only Markdown skill files. No scripts, binaries, or background processes are installed.
• User confirmation required — All write operations (create events, send messages, create tasks, etc.) require explicit user confirmation before execution.
• Scope transparency — Each skill declares its required OAuth scopes in a permission table. Use per-skill --domain auth to grant only the minimum permissions needed.
• Graceful degradation — Optional domains that fail or are unauthorized are skipped with a notice, never blocking the main workflow.

Contributing

We welcome contributions! See CONTRIBUTING.md for guidelines.

License

This project is licensed under the MIT License — see LICENSE for details.

This software calls Lark/Feishu Open Platform APIs at runtime. Use of these APIs is subject to the Lark Terms of Service and Privacy Policy.