
Wecomcli Get Todo Detail
Batch-fetch WeCom (企业微信) todo bodies and assignees by ID after listing todos via wecom-cli.
Overview
Wecomcli Get Todo Detail is an agent skill for the Build phase that batch-queries 企业微信 todo content and assignees by ID through wecom-cli.
Install
npx skills add https://github.com/wecomteam/wecom-cli --skill wecomcli-get-todo-detailWhat is this skill?
- Batch detail via wecom-cli todo get_todo_detail—up to 20 todo_id values per call
- Mandatory ID-to-name pass: resolve follower_id and creator_id with contact get_userlist before showing users
- HTTP error retry up to three attempts
- Designed to chain after wecomcli-get-todo-list for ID discovery
- Requires wecom-cli binary on PATH
- Up to 20 todo IDs per get_todo_detail request
- Up to 3 retries on HTTP errors
Adoption & trust: 2.4k installs on skills.sh; 2.2k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have WeCom todo IDs from a list call but users only see meaningless follower_id and creator_id strings without names or full descriptions.
Who is it for?
Builders running wecom-cli-backed agents who need full todo text and assignee names after listing todos.
Skip if: Creating or completing todos, or environments without wecom-cli installed and authenticated.
When should I use this skill?
User wants todo content, assignees, or full detail for specific WeCom todo IDs—phrases like 看看这个待办的详情 or 这个待办分派给谁了; typically after listing todos.
What do I get? / Deliverables
You present named creators and followers with todo content and status, ready for follow-up actions in chat or workflow.
- Todo content, status, and follower list with resolved display names
- Structured CLI JSON response interpreted for the user
Recommended Skills
Journey fit
WeCom CLI integration is wired during product build when you connect agents to enterprise collaboration APIs. Integrations subphase fits command-line bridges that read todo content and followers from WeCom Open Platform.
How it compares
Detail fetch companion to wecomcli-get-todo-list—not a general project-management MCP or standalone WeCom OAuth tutorial.
Common Questions / FAQ
Who is wecomcli-get-todo-detail for?
Indie builders and operators automating 企业微信 with wecom-cli who need readable todo details for agents or scripts.
When should I use wecomcli-get-todo-detail?
In Build integrations when a user asks what a todo says, who it is assigned to, or wants full detail after you already have todo IDs from the list skill.
Is wecomcli-get-todo-detail safe to install?
It runs shell commands against your WeCom tenant; review Security Audits on this page and scope CLI credentials to least privilege.
Workflow Chain
Requires first: wecomcli get todo list
Then invoke: wecomcli lookup contact
SKILL.md
READMESKILL.md - Wecomcli Get Todo Detail
# 企业微信待办详情查询技能 > `wecom-cli` 是企业微信提供的命令行程序,所有操作通过执行 `wecom-cli` 命令完成。 通过 `wecom-cli` 根据待办 ID 列表批量查询完整详情,包含待办内容和分派人信息。 ## 行为策略 **人员 ID 转姓名(关键步骤)**: 返回结果中的 `follower_id` 和 `creator_id` 都是系统内部 ID,直接展示给用户毫无意义——用户不认识这些 ID,只认识姓名。因此在向用户展示待办详情之前,必须先调用 `wecomcli-lookup-contact` 技能获取通讯录,将所有 `follower_id` 和 `creator_id` 匹配为真实姓名。具体做法: ```bash wecom-cli contact get_userlist '{}' ``` 如果通讯录中找不到某个 ID,展示时标注"未知用户(ID: xxx)"即可。 **重试策略**: 遭遇"返回 HTTP 错误"或"HTTP 请求失败"时,主动重试,最多重试三次。 --- ## 调用方式 ```bash wecom-cli todo get_todo_detail '<json格式的入参>' ``` ## 参数说明 | 参数 | 类型 | 必填 | 说明 | |------|------|------|------| | `todo_id_list` | array | ✅ | 待办 ID 列表,最多 20 个 | **调用示例:** ```bash wecom-cli todo get_todo_detail '{"todo_id_list": ["TODO_ID_1", "TODO_ID_2"]}' ``` ## 返回格式 ```json { "errcode": 0, "errmsg": "ok", "data_list": [ { "todo_id": "TODO_ID", "todo_status": 1, "content": "完成Q2规划文档", "follower_list": { "followers": [ { "follower_id": "FOLLOWER_ID", "follower_status": 1, "update_time": "2025-01-16 14:20:00" } ] }, "creator_id": "CREATOR_ID", "user_status": 1, "remind_time": "2025-06-01 09:00:00", "create_time": "2025-01-15 10:30:00", "update_time": "2025-01-16 14:20:00" } ] } ``` ## 返回字段说明 | 字段 | 类型 | 说明 | |------|------|------| | `data_list` | array | 待办详情列表,最多 20 条 | | `data_list[].todo_id` | string | 待办 ID | | `data_list[].todo_status` | number | 待办状态:`0`-已完成,`1`-进行中,`2`-已删除 | | `data_list[].content` | string | 待办内容 | | `data_list[].follower_list.followers` | array | 分派人列表 | | `data_list[].follower_list.followers[].follower_id` | string | 分派人 ID(即 userid)— **展示前需通过 wecomcli-lookup-contact 转为姓名** | | `data_list[].follower_list.followers[].follower_status` | number | 分派人状态:`0`-拒绝,`1`-接受,`2`-已完成 | | `data_list[].follower_list.followers[].update_time` | string | 分派人状态更新时间 | | `data_list[].creator_id` | string | 创建人 ID — **展示前需通过 wecomcli-lookup-contact 转为姓名** | | `data_list[].user_status` | number | 当前用户状态 | | `data_list[].remind_time` | string | 提醒时间 | | `data_list[].create_time` | string | 创建时间 | | `data_list[].update_time` | string | 更新时间 | --- ## 典型工作流 ### 列表 + 详情联合查询(三步缺一不可) 用户问:"看看我最近的待办" / "我有哪些待办事项?" 1. 第一步:通过 wecomcli-get-todo-list 获取待办列表。 ```bash wecom-cli todo get_todo_list '{}' ``` 2. 第二步:根据返回的 todo_id 批量获取详情。 ```bash wecom-cli todo get_todo_detail '{"todo_id_list": ["TODO_ID_1", "TODO_ID_2", "TODO_ID_3"]}' ``` 3. 第三步(不要跳过!):通过 wecomcli-lookup-contact 获取通讯录,将 follower_id / creator_id 转为姓名。用返回的 userlist 中的 userid 匹配 follower_id 和 creator_id,取 name 字段作为展示姓名 > 第三步是展示可读结果的前提。没有这一步,用户看到的是一串无意义的 ID 而非姓名。 **展示格式(注意:分派人和创建人必须显示为姓名,不是 ID):** ``` 📋 您当前的待办事项(共 3 项) 1. 🔵 完成Q2规划文档 - 待办状态:进行中 | 我的状态:已接受 - 提醒时间:2025-06-01 09:00 - 分派人:张三、李四 - 创建时间:2025-01-15 2. 🔵 提交周报 - 待办状态:进行中 | 我的状态:已接受 - 提醒时间:2025-03-17 18:00 - 创建时间:2025-03-10 3. ☑️ 代码评审 - 待办状态:已完成 | 我的状态:已完成 - 创建时间:2025-03-01 ``` --- ## 注意事项 1. **人员 ID 必须转姓名** - 返回结果中的 `follower_id` 和 `creator_id` 是系统内部标识,用户无法识别 - 展示待办详情前,先 ```bash wecom-cli contact get_userlist '{}' ``` 获取通讯录 - 用通讯录的 `userid` 匹配 `follower_id` / `creator_id`,用 `name` 替换展示 2. **todo_id 来源规则** - `todo_id` 必须来自 `wecomcli-get-todo-list` 返回的结果,禁止自行推测或构造 - 用户通常提供待办内容描述而非 ID,应先通过 `wecomcli-get-todo-list` 查列表再匹配 3. **状态值含义** - 待办状态(`todo_status`):`0`-已完成,`1`-进行中,`2`-已删除 - 用户状态(`user_status`):`0`-拒绝,`1`-接受,`2`-已完成 - 分派人状态(`follower_status`):`0`-拒绝,`1`-接受,`2`-已完成