enterprise-workflow

Creates documents, tables, tasks, meetings, and slides in WeCom and Lark via callback APIs.

2.9k|733|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/zts212653/clowder-ai --skill enterprise-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enterprise-workflow
Source: https://github.com/zts212653/clowder-ai/tree/main/cat-cafe-skills/enterprise-workflow
Command: npx skills add https://github.com/zts212653/clowder-ai --skill enterprise-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating enterprise IM work artifacts—documents, spreadsheets, todos, meetings, and calendar events—normally requires manual creation across WeCom or Lark consoles. This Skill automates one-shot creation of these resources through vendor CLI-backed callback routes, including a golden chain that turns one sentence into a full document + table + task + meeting workflow.

Core Features & Use Cases

  • Dual-platform support: Routes actions to WeCom (/api/callbacks/wecom-action) or Lark (/api/callbacks/lark-action) based on which platform the operator mentions.
  • Individual resource creation: Create docs, smart tables/bitables, todos/tasks, meetings/calendar events, and Lark-exclusive slides with structured JSON payloads.
  • Golden chain workflow: One request generates a document, tracking table, assigned tasks, and a scheduled meeting (plus optional slides on Lark) in a single call.
  • Use Case: An operator says "create a Q2 PRD workflow in Feishu"—the Skill posts a golden_chain action to the Lark callback and returns links to the generated doc, bitable, tasks, and calendar event.

Quick Start

Ask the assistant to create a document, task list, and review meeting in WeCom or Lark, and it will invoke the golden_chain callback and reply with the generated resource links.

Frequently Asked Questions about enterprise-workflow

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

FAQPage Schema
How do I create a document and meeting in WeCom or Lark automatically?

Send a POST request to /api/callbacks/wecom-action or /api/callbacks/lark-action with the golden_chain action, including doc name, tasks, and meeting details. The callback returns links to the created document, table, tasks, and meeting.

What is the difference between WeCom and Lark actions in this workflow?

WeCom supports create_doc, create_smart_table, create_todo, and create_meeting, while Lark supports create_doc, create_base, create_task, create_calendar_event, and create_slides. Lark's golden chain additionally includes slides, which WeCom does not offer.

Can I call wecom-cli or lark-cli directly instead of the callback route?

No. All operations must go through the callback routes (/api/callbacks/wecom-action or lark-action) per ADR-029. Calling the CLI directly breaks the audit chain and is explicitly prohibited.

How do I get user IDs for assigning tasks in WeCom and Lark?

For WeCom, query the directory through the Hub via TypeScript import, or use the operator's own userId in demos. For Lark, use known open_id values (ou_xxx); searchUsers requires contact:contact.search authorization.

Why does the workflow return a 502 or 503 error?

A 502 error with a code and msg means the vendor API (WeCom or Lark) rejected the request, often due to missing API permissions. A 503 error means the required CLI (wecom-cli or lark-cli) is not installed or not logged in.