Meegle
Query and mutate Meegle (Lark) spaces, stories, and defects from the agent via the meegle CLI with JSON output for programmatic PM workflows.
Overview
Meegle is an agent skill for the Build phase that teaches the Meegle CLI to search spaces, query work items with MQL, and create or update stories and defects with JSON output.
Install
npx skills add https://github.com/larksuite/meegle-cli --skill meegleWhat is this skill?
- Project search and paginated listing of spaces the user can access
- Work-item metadata: meta-types, meta-fields, meta-roles with filters
- MQL workitem query and get/create with scalar and multi-user fields
- All examples use --format json for agent-parseable responses
- Covers story/defect flows with project-key and work-item-type parameters
Adoption & trust: 973 installs on skills.sh; 121 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent needs to read or update Lark Meegle backlog items but you only have fragmented API knowledge and no consistent CLI recipes.
Who is it for?
Solo builders on Lark/Meegle who want agent-driven backlog queries and ticket creation from the terminal.
Skip if: Teams not using Meegle/Lark project management or anyone who needs a hosted MCP server instead of CLI invocation.
When should I use this skill?
When automating Lark Meegle spaces, MQL queries, or work-item create/get from an agent session.
What do I get? / Deliverables
You get copy-paste meegle commands for project search, metadata discovery, MQL query, get, and create so the agent can sync PM state with your build workflow.
- Executed meegle commands with --format json
- Created or updated work items in Meegle
Recommended Skills
Journey fit
Work-item and project APIs sit in Build when wiring delivery tooling into your stack. Meegle is an external PM platform integration, not app UI or backend code.
How it compares
Use as a procedural CLI cookbook for Meegle, not as a generic issue-tracker MCP or GitHub Issues skill.
Common Questions / FAQ
Who is meegle for?
Indie and solo developers (and small teams) who run delivery on Lark Meegle and want their coding agent to list spaces, run MQL, and create work items via the official meegle CLI.
When should I use meegle?
During Build when integrating PM tooling—pull open stories before a sprint task, file a defect after a repro, or resolve project-key and field metadata before automating creates.
Is meegle safe to install?
Treat it like any third-party skill: review the Security Audits panel on this Prism page and scope CLI credentials; commands can create and modify real work items in your Lark tenant.
SKILL.md
READMESKILL.md - Meegle
# 命令调用示例 --- ## 空间域 ### project search 已知空间名/key： ```bash meegle project search --project-key 空间名或key --page-num {{page_num}} --format json ``` 列出当前用户可访问的空间（按最近访问排序，分页）： ```bash meegle project search --project-key {{project_key}} --page-num 1 --format json ``` ## 工作项域 ### workitem meta-types ```bash meegle workitem meta-types --project-key 空间key --format json ``` ### workitem meta-fields 查询所有字段： ```bash meegle workitem meta-fields --page-num 1 --project-key 空间key --work-item-type story --field-types '{{field_types}}' --field-keys '{{field_keys}}' --field-query '{{field_query}}' --format json ``` ### workitem meta-roles ```bash meegle workitem meta-roles --page-num 1 --project-key 空间key --work-item-type story --role-keys '{{role_keys}}' --role-query '{{role_query}}' --format json ``` ### workitem query 查询空间中所有未冻结的需求： ```bash meegle workitem query --project-key 空间key --session-id {{session_id}} --mql 'SELECT `work_item_id`, `name`, `current_owners`, `status` FROM `空间名`.`story` WHERE `is_archived` = 0' --group-pagination-list '{{group_pagination_list}}' --format json ``` ### workitem get ```bash meegle workitem get --work-item-id 工作项ID或名称 --fields '{{fields}}' --project-key 空间key --format json ``` ### workitem create 基础创建（仅标量字段）： ```bash meegle workitem create --work-item-type story --fields '[{"field_key": "template", "field_value": "模板ID"}, {"field_key": "name", "field_value": "需求标题"}]' --project-key 空间key --format json ``` 创建缺陷 + 指定报告人（multi-user）+ 指定经办人（role_owners）——注意复合值必须 JSON.stringify： ```bash meegle workitem create --work-item-type issue --fields '[{"field_key":"name","field_value":"示例缺陷"},{"field_key":"priority","field_value":"2"},{"field_key":"template","field_value":"模板ID"},{"field_key":"issue_reporter","field_value":"["userkey1"]"},{"field_key":"role_owners","field_value":"[{"role":"operator","owners":["userkey1"]}]"}]' --project-key 空间key --format json ``` > 🚨 `issue_reporter`（multi-user 类型的内置角色字段）和 `role_owners`（统一角色入口）是**两种可互换的写法**：前者走 meta-create-fields 返回的字段 key；后者用 meta-roles 返回的 role_id（如 `operator` / `reporter`，不含 `issue_` 前缀）。两者的 `field_value` 都必须是 **stringified JSON** 字符串。 ### workitem update 更新普通字段： ```bash meegle workitem update --work-item-id 工作项ID --project-key 空间key --role-operate '{{role_operate}}' --fields '[{"field_key": "priority", "field_value": "option_id"}]' --format json ``` 更新 multi-user 字段（复合值 stringified）： ```bash meegle workitem update --work-item-id 工作项ID --project-key 空间key --role-operate '{{role_operate}}' --fields '[{"field_key": "current_status_operator", "field_value": "["userkey1","userkey2"]"}]' --format json ``` --- ## 人员域 ### user search ```bash meegle user search --user-keys '["张三", "李四"]' --project-key {{project_key}} --format json ``` ### user me ```bash meegle user me --format json ``` --- ## 工作台域 ### mywork todo 查询我的待办： ```bash meegle mywork todo --action todo --page-num 1 --asset-key {{asset_key}} --format json ``` --- ## 工时域 ### workhour list-schedule ```bash meegle workhour list-schedule --start-time 2025-03-01 --end-time 2025-03-31 --project-key 空间key --user-keys '["张三", "李四"]' --work-item-type-keys '{{work_item_type_keys}}' --format json ``` --- ## 视图域 ### view get ```bash meegle view get --view-id 视图ID --project-key 空间key --fields '{{fields}}' --page-num {{page_num}} --format json ``` --- ## 工作流域 ### workflow get-node ```bash meegle workflow get-node --work-item-id 工作项ID --field-key-list '{{field_key_list}}' --need-sub-task {{need_sub_task}} --page-num {{page_num}} --project-key 空间key --node-id-list '["节点ID或_all"]' --format json ``` ### workflow transition 完成节点（节点流）： ```bash meegle workflow transition --work-item-id 工作项ID --node-ids '{{node_ids}}' --project-key 空间key --node-id 节点ID --action confirm --rollback-reason '{{rollback_reason}}' --format json ``` ### workflow transition-state 流转状态（状态流）： ```bash meegle workflow transition-state --work-item-id 工作项ID --project-key 空间key --transition-id 流转ID --format json ``` ### workf