prompt
FreeLark/Feishu automation architect with production-grade response contract
FreeFree tier
Inputs: textOutputs: text, code
About prompt
A detailed prompt for designing cross-service automation workflows across the entire Lark/Feishu ecosystem. It treats every script as production infrastructure—versioned, auditable, and reversible. The prompt enforces a strict response contract covering assumptions floor, risk categories, automation pattern tradeoffs, validation plans, and rollback notes. Covers 12 Lark services (Messenger, Docs, Drive, Sheets, Base, Slides, Calendar, Mail, Tasks, Meetings, Approval, Attendance) plus Markdown, with key CLI shortcuts and common pitfalls for each. Requires --dry-run before any destructive operations.
Key Features
Strict response contract: assumptions, risk category, tradeoffs, validation plan, rollback notes
Coverage of 12 Lark services plus Markdown with CLI shortcuts and common pitfalls
Enforces `--dry-run` before destructive operations (bulk delete, permission changes)
Treats every automation as production infrastructure: versioned, auditable, reversible
Includes rollback notes with undo windows (Drive trash retention, Mail grace period, Base revision history)
Service Coverage Matrix with core automations per service
Pros & Cons
Pros
- Comprehensive across all major Lark services
- Production-grade approach with versioning and auditability
- Includes safety mechanisms (dry-run, rollback plans, undo windows)
- Structured response contract ensures clarity and risk mitigation
Cons
- Requires familiarity with Lark CLI and APIs
- Limited to Lark/Feishu ecosystem only
- May be overly verbose for simple one-off automations
Best For
Automating Messenger chat ops (send/reply, group lifecycle, thread management)Template-based document generation and bulk append/replace in DocsDrive file management, bulk operations, and sharing auditsSheets data manipulation and bulk updatesBase (database) record creation, updates, and bulk operationsSlides automation for presentation generation and batch editsCalendar event management, sync, and schedulingMail inbox automation, deletion grace period management
FAQ
What is the response contract in this prompt?
Every response must include: 1) Assumptions scope floor (target services, identity model, execution context, tenant type, data residency); 2) Risk category addressed (e.g., permission sprawl, rate-limit exhaustion); 3) Chosen automation pattern tradeoffs; 4) Validation plan with exact `--dry-run` steps; 5) Rollback notes for any write/delete/permission change.