dingtalk-todo
钉钉待办 / TODO。Use when 用户说 创建待办/TODO/任务提醒/指派任务/标记完成/查待办/紧急待办/循环待办/批量建待办/逾期待办。Distinct from dingtalk-report(日报周报)、dingtalk-oa(审批)、dingtalk-calendar(日程)。命令前缀:dws todo。
pinned to #fc9acb9updated 2 weeks ago
Ask your AI client: “install skills/dingtalk-todo”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/dingtalk-todometahub onboarded this repo on the author's behalf.
If you own github.com/DingTalk-Real-AI/dingtalk-workspace-cli on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
2,377
Last commit
2 weeks ago
Latest release
published
About this skill
Pulled from SKILL.md at publish time.
> 🧪 **EXPERIMENTAL · 试验版 / Preview** — multi 模式当前未达 stable 标准。22 个 dingtalk-* skill 全部通过 dispatch verifier,但接口、命名、跨 skill 引用后续可能调整;生产 / 共享环境请优先使用 mono 模式(`dws skill setup --mode mono`)。问题请提 issue 反馈。
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.fc9acb9· 2 weeks ago
Documentation
41Description quality
64 words · 163 chars — "钉钉待办 / TODO。Use when 用户说 创建待办/TODO/任务提醒/指派任务/标记完成/查待办/紧急待办/循环待办/批量建待办/逾期待办。Disti…"
README is present and substantial
32,991 chars · 12 sections · 25 code blocks
Tags / topics declaredwarn
No manifest tags and no GitHub repo topics
Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.
README has usage / example sections
found: Installation · Getting Started · Quick Start
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Release history
1- releasecurrentfc9acb9warn2 weeks ago
Contents
钉钉待办 Skill
🧪 EXPERIMENTAL · 试验版 / Preview — multi 模式当前未达 stable 标准。22 个 dingtalk-* skill 全部通过 dispatch verifier,但接口、命名、跨 skill 引用后续可能调整;生产 / 共享环境请优先使用 mono 模式(
dws skill setup --mode mono)。问题请提 issue 反馈。
PREREQUISITE: Read the
dws-sharedskill first for auth, global flags, product routing, URL preflight, error codes, and safety rules. Thedwsbinary must be on PATH.
⚠️ 命令可用性以当前 dws 二进制为准。服务发现已下线,本文档随内置 skill 发布;如果
dws <cmd> --help不存在,说明当前版本未暴露该命令。若命令存在但调用失败,请按错误中的 endpoint 或 tool 提示确认静态端点目录和后端工具注册。实际调用前可用dws <cmd> --help或--dry-run验证。
命令参考:todo.md;剧本:02-task.md。
意图表
| 用户说 | 命令 |
|---|---|
| "建一条待办给张三" | dws todo task create --title "<标题>" --executors <userId> |
| "较高 / 高优先级待办" | dws todo task create ... --priority 30(10低/20普通/30较高/40紧急) |
| "紧急 / 最高优先级 / 立即处理" | dws todo task create ... --priority 40 |
| "循环待办(每天)" | dws todo task create ... --due "<首次截止ISO>" --recurrence "DTSTART:<UTC>\nRRULE:FREQ=DAILY;INTERVAL=1" |
| "批量建待办(JSON 文件)" | python scripts/todo_batch_create.py todos.json |
| "今天 / 本周未完成待办" | python scripts/todo_daily_summary.py [today|tomorrow|week] |
| "逾期待办" | python scripts/todo_overdue_check.py |
| "标记完成 / 重开" | dws todo task done --task-id <taskId> --status true|false |
| "修改标题/截止时间/优先级" | dws todo task update --task-id <taskId> ... |
| "删除待办" | dws todo task delete --task-id <taskId>(需用户确认) |
参数硬约束
- 任务详情只用
dws todo task get --task-id <taskId>;不要写task detail。 - 完成状态首选
dws todo task done --task-id <taskId> --status true|false;若用update,也必须是--task-id+--done true|false。 - 查询列表完成状态用
dws todo task list --status false|true --format json。不要写--done true作为可见参数,虽然兼容但不作为推荐写法。 --id/--ids是隐藏兼容别名,文档和生成命令统一写--task-id,减少模型漂移。- 优先级映射:低=10,普通=20,较高/高/重要=30,紧急/最高/P0/马上处理=40;不要把"较高"写成 40。
- 截止时间必须是 ISO-8601。相对日期按当前日期计算;例如周五说"下周二"就是紧接下一个自然周的周二,不要再加一周。
- 附件命令
task add-attachment/list-attachment/remove-attachment均可用:add-attachment --task-id <taskId> --file-path <本地文件>(真实上传,先确认待办存在,返回result.attachmentIds);list-attachment --task-id <taskId>(返回顶层attachments[].attachmentId);remove-attachment --task-id <taskId> --attachment-id <id> --yes(不可逆,先确认)。 - 创建、标记完成、重开、删除后必须
task get或对应task list --status ...验证,不要只凭创建返回或口头计划结束。 - 所有 dws 命令带
--format json。
跨产品协作
- 执行人是人名 → 先用
dingtalk-aisearch拿userId - 会后从听记自动建待办 → 切到
dingtalk-minutes - 项目进度汇总写文档 → 切到
dingtalk-doc
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/dingtalk-todo