wecom-get-todo-detail

Batch query WeCom todos by ID and map assignee names.

1|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/polaris-dxz/xclaw --skill wecom-get-todo-detail-polaris-dxz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wecom-get-todo-detail
Source: https://github.com/polaris-dxz/xclaw/tree/main/apps/desktop/openclaw-runtime/config/extensions/wecom-openclaw-plugin/skills/wecom-get-todo-detail
Command: npx skills add https://github.com/polaris-dxz/xclaw --skill wecom-get-todo-detail-polaris-dxz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrieve detailed information for multiple WeCom todos by ID, including content and assignee data, to replace opaque IDs with readable details and save manual lookup effort.

Core Features & Use Cases

  • Batch detail retrieval: given a list of todo IDs, fetch full details for each item, including content and assignment data.
  • ID-to-name mapping: convert follower_id and creator_id to human-friendly names via wecom-contact-lookup before presenting results.
  • Reliability & safety: automatic retries on transient failures (up to three attempts) and clear error handling when IDs are invalid or APIs fail.
  • Workflow integration: typically used after wecom-get-todo-list to first obtain IDs, then fetch details in a single flow.

Quick Start

Provide a JSON array of todo_id_list to fetch detailed information for each item, including content and assignee names.

Frequently Asked Questions about wecom-get-todo-detail

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

FAQPage Schema
How do I batch retrieve WeCom todo details using a list of IDs?

To batch retrieve WeCom todo details, provide a JSON array of todo IDs. The Skill fetches full details for each item, including content and assignee data, replacing opaque IDs with readable information.

Can I map internal WeCom user IDs to readable names when fetching todo details?

Yes, you can map internal IDs to names. The Skill converts follower_id and creator_id fields to human-friendly names via the wecom-contact-lookup integration before presenting the final todo details results.

What happens if an API call fails or I provide invalid IDs to fetch WeCom todos?

If an API call fails or IDs are invalid, the Skill handles failures with automatic retries up to three times. It then surfaces actionable error messages to help you identify and resolve the invalid input.

Do I need to get a todo ID list before fetching WeCom todo details in bulk?

Yes, you need a todo ID list first. You typically obtain these IDs by applying the wecom-get-todo-list Skill, then pass the resulting list directly to fetch complete WeCom todo details in a single workflow.

What specific data is included when I query WeCom todos by ID?

Querying WeCom todos by ID retrieves full details for each item. The response includes the todo content and assignee data, specifically mapping follower_id and creator_id to human-readable names.

Why does my WeCom todo bulk detail retrieval stop working after a transient failure?

Transient failures trigger automatic retries up to three attempts. If the WeCom todo detail retrieval stops working, it means the API calls failed after three retries or the provided IDs are invalid, surfacing actionable error messages.