负责钉钉消息发送的所有操作。本文件为策略指南；完整 API 请求格式、场景路由、消息类型速查、身份标识、错误码等见 references/api.md。
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondingtalk-messageExecute the skills CLI command in your project's root directory to begin installation:
Fetches dingtalk-message from breath57/dingtalk-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate dingtalk-message. Access via /dingtalk-message in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
44
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
44
stars
负责钉钉消息发送的所有操作。本文件为策略指南；完整 API 请求格式、场景路由、消息类型速查、身份标识、错误码等见 references/api.md。
dt_helper.sh位于本SKILL.md同级目录的scripts/dt_helper.sh。
| 通道 | 适用场景 | Token | 特点 |
|---|---|---|---|
| Webhook 机器人 | 往指定群发通知 | 无需 | 最简单；URL 自带凭证 |
| 企业内部应用机器人 | 单聊私信 / 群聊 | --token（新版） |
可撤回、查已读 |
| 工作通知 | 应用推送到"工作通知" | --old-token（旧版） |
可推全员/部门 |
| sessionWebhook | 回调中直接回复 | 无需 | 回调消息自带临时 URL |
bash scripts/dt_helper.sh --get KEY 读取该通道所需键值bash scripts/dt_helper.sh --set KEY=VALUE 写入--token；工作通知用 --old-token；Webhook/sessionWebhook 无需/tmp/<task>.sh 再执行；禁止 heredoc| 通道 | 所需配置 | 来源说明 |
|---|---|---|
| Webhook | DINGTALK_WEBHOOK_URL（加签额外需 DINGTALK_WEBHOOK_SECRET） |
群设置 → 智能群助手 → 添加自定义机器人 |
| 机器人消息 | DINGTALK_APP_KEY + DINGTALK_APP_SECRET |
开放平台 → 应用管理 → 凭证信息 |
| 工作通知 | DINGTALK_APP_KEY + DINGTALK_APP_SECRET + DINGTALK_AGENT_ID |
agentId 在应用管理 → 基本信息 |
robotCode=appKey（完全一致，无需额外配置）- 凭证禁止在输出中完整打印，确认时仅显示前 4 位 +
****- 消息内容缺失时：先询问用户想发什么，不要自行编造
消息 API 只接受 userId（staffId），不接受 unionId。详见 grep -A 20 "^## 身份标识" references/api.md。
bash scripts/dt_helper.sh --to-userid <unionId>grep -A 20 "^### 群消息发送方式选择" references/api.md#!/bin/bash
set -e
HELPER="./scripts/dt_helper.sh"
TOKEN=$(bash "$HELPER" --token)
USER_ID=$(bash "$HELPER" --get DINGTALK_MY_USER_ID | cut -d= -f2)
# 机器人单聊示例
RESP=$(curl -s -w '\nHTTP_STATUS:%{http_code}' -X POST "https://api.dingtalk.com/v1.0/robot/oToMessages/batchSend" \
-H "x-acs-dingtalk-access-token: $TOKEN" \
-H "Content-Type: application/json" \
-d '{"robotCode":"'$(bash "$HELPER" --get DINGTALK_APP_KEY | cut -d= -f2)'","userIds":["'$USER_ID'"],"msgKey":"sampleText","msgParam":"{\"content\":\"测试消息\"}"}')
echo "$RESP"
#!/bin/bash
set -e
HELPER="./scripts/dt_helper.sh"
OLD_TOKEN=$(bash "$HELPER" --old-token)
AGENT_ID=$(bash "$HELPER" --get DINGTALK_AGENT_ID | cut -d= -f2)
USER_ID=$(bash "$HELPER" --get DINGTALK_MY_USER_ID | cut -d= -f2)
# 工作通知示例
RESP=$(curl -s -w '\nHTTP_STATUS:%{http_code}' -X POST "https://oapi.dingtalk.com/topapi/message/corpconversation/asyncsend_v2?access_token=$OLD_TOKEN" \
-H "Content-Type: application/json" \
-d '{"agent_id":"'$AGENT_ID'","userid_list":"'$USER_ID'","msg":{"msgtype":"text","text":{"content":"测试工作通知"}}}')
echo "$RESP"
Token 异常时：
bash "$HELPER" --token --nocache或bash "$HELPER" --old-token --nocache
grep -A 196 "^## 一、群自定义 Webhook 机器人" references/api.md
grep -A 192 "^## 二、企业内部应用机器人" references/api.md
grep -A 145 "^## 三、工作通知" references/api.md
grep -A 60 "^## 四、sessionWebhook" references/api.md
grep -A 30 "^## 场景路由" references/api.md
grep -A 20 "^### 群消息发送方式选择" references/api.md
grep -A 25 "^## 身份标识" references/api.md
grep -A 30 "^## 消息类型速查" references/api.md
grep -A 33 "^## 错误码" references/api.md
grep -A 12 "^## 所需应用权限" references/api.md
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
We added dingtalk-message from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in dingtalk-message — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
dingtalk-message has been reliable in day-to-day use. Documentation quality is above average for community skills.
dingtalk-message fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: dingtalk-message is focused, and the summary matches what you get after install.
dingtalk-message is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: dingtalk-message is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added dingtalk-message from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
dingtalk-message has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend dingtalk-message for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 34