Manage WeCom todos via wecom-cli with create, list, update, finish, and delete operations.
npx skills add https://github.com/YanHaidao/wecom --skill wecomcli-todo-yanhaidao
Please help me install this Agent Skill. Skill: wecomcli-todo Source: https://github.com/YanHaidao/wecom/tree/main/skills/wecomcli-todo Command: npx skills add https://github.com/YanHaidao/wecom --skill wecomcli-todo-yanhaidao
deadline object (date vs datetime) with remind_at_deadline handling, including guidance for 'remind X minutes early' requests that the API cannot directly set. - Idempotent, Safe Operations: Locates todos via list before mutating, distinguishes creator-delete vs participant-exit semantics, and avoids duplicate finish calls. - Use Case: A user says 'Remind me to prepare the weekly report Friday at 9am and assign it to vincentwei'—the skill resolves the assignee, builds the deadline object, creates the todo, and echoes back title, participants, and deadline. ## Quick Start Ask the assistant to create a WeCom todo such as 'add a todo to submit the expense report by next Friday' and it will handle the rest through wecom-cli.High-intent search queries and answers about installing and using this skill.
Call wecom-cli todo create with a JSON body containing items, each with a title and an optional deadline object. Use type datetime with remind_at_deadline=true to remind at the exact deadline moment, or type date for date-only deadlines with default advance reminder.
Use wecom-cli todo list with status_filter (finished or proceed), keywords arrays for OR/AND matching, and optional create or deadline time ranges. Note that omitting status_filter returns only in-progress todos, and use --page-count to fetch all pages.
The API cannot directly set an advance reminder offset; deadline always stores the actual due time. After creating, check the returned extra_info, and if it does not match the requested advance time, the user must adjust the reminder manually in the WeCom todo app.
The same delete interface works for non-creators, but the semantic is exiting the todo rather than deleting it for everyone. Only the creator's delete removes the entire todo for all participants, so the skill checks the creator field to phrase the result correctly.
When the current user is both creator and participant, the backend returns ask_finish_all after marking only their own part complete. The skill then asks the user to choose between finishing only their part or marking the entire todo finished with finished_all=true.
LiangdiCreate, update, delete, and change user status of WeCom todo items via the wecom-pro CLI.
openshift-engGenerate a Slack-ready daily standup report from an IC TODO markdown file.
PinvouManage the full lifecycle of WeCom online meetings via the wecom-cli command line.
WecomTeamCoordinate enterprise calendars in WeCom with querying, event creation, updates, and availability checks.