飞书项目（Meego/Meegle）操作工具。支持查询和管理工作项、节点流转、视图查询、个人待办、排期统计等功能。 Use when user needs to work with Feishu/Lark Meego project management — including querying work items, creating/updating work items, completing workflow nodes, checking views, listing todos, analyzing schedules/workloads, or searching with MQL. 关键词：飞书项目、meego、meegle、工作项、需求、任务、缺陷、排期、视图、待办、节点。
Meegle is an operations toolkit for Feishu Project (also known as Meego or Meegle) that works through the Meegle CLI to query and manage project data. It supports working with work items (requirements, tasks, and defects), node transitions, view queries, personal to-dos, and schedule or workload statistics, and it is meant to be used when a user needs to query, create, or update work items, complete workflow nodes, check views, list to-dos, analyze schedules, or search with MQL. Output follows the user's input language and defaults to Chinese, and every business command must first pass an authorization flow described in a referenced auth-guard document, with companion references covering CLI usage, API examples, and MQL syntax.
The skill is organized into domains. The Project domain includes project search to convert a space name into a project_key or verify a space exists. The WorkItem domain covers create (which requires first fetching field and role metadata and a mandatory template ID), get, batch-get (a client-side fan-out with a limit of 200 IDs at 3 concurrency), update, MQL-based query with grouped pagination, and operation-record listing, plus metadata commands for types, fields, and roles. It documents important subtleties such as the group_type logical field that merges physical group fields, where the read payload uses value as the discriminator while writes use type, and CLI quirks like needing to pass page_size and page_token through --params so they serialize as numbers rather than strings.
The Attachment domain handles two-step signed uploads and downloads to object storage, with one-shot +upload and +download wrappers. The WorkFlow domain distinguishes node-flow work items (workflow transition with confirm or rollback actions) from state-flow work items (workflow transition-state using a transition_id fetched from list-state-transitions), and includes get-node and update-node for editing schedules, owners, and custom fields, noting that schedule, differentiated schedule, and owners must be updated in separate calls. The MyWork domain provides mywork todo to list the current user's work items by action type without needing MQL. Throughout, the doc repeatedly directs users to fetch metadata via meta-fields and meta-roles before creating or updating, and points to reference files for detailed parameter tables and standard operating procedures.
An authorization flow described in references/auth-guard.md must be executed before all business commands. The skill also directs you to CLI, API example, and MQL syntax references for command structure and usage.
You must first use workitem meta-fields to get field information and workitem meta-roles to get role information, and the template ID is mandatory. You pass the work item type and optionally fields and other flags.
The workitem query command takes a project-key and an MQL statement (full SQL). Results are paginated up to 50 per page, using session_id and group-pagination-list for paging, and it recommends selecting by field key and fetching field and role metadata first.
The server merges physical group fields like group_id and chat_group into one logical field, group_type. Read and write both go through group_type, but the read payload uses value as the discriminator while updates use type, so you should not write back the read structure directly.
workflow transition is only for node-flow work items and uses confirm or rollback actions on nodes, while workflow transition-state is only for state-flow work items and moves state using a transition_id obtained from workflow list-state-transitions.
Quick Setup:
.claude/skills/Repository
larksuite/meegle-cli