Agent skill

Dingtalk Openapi Skill

Operate DingTalk messaging APIs through UXC with a curated OpenAPI schema, app-token bearer auth, and robot/service-group guardrails.

MITAuto-check passedBackend & APIs

Install Dingtalk Openapi Skill

skills CLI

$ npx skills add holon-run/uxc --skill dingtalk-openapi-skill -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install holon-run/uxc dingtalk-openapi-skill --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/holon-run/uxc.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/dingtalk-openapi-skill .claude/skills/dingtalk-openapi-skill && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "dingtalk-openapi-skill" agent skill from https://github.com/holon-run/uxc/tree/main/skills/dingtalk-openapi-skill into .claude/skills/dingtalk-openapi-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dingtalk-openapi-skill", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/holon-run/uxc/tree/main/skills/dingtalk-openapi-skill

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add holon-run/uxc --skill dingtalk-openapi-skill -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install holon-run/uxc dingtalk-openapi-skill --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/holon-run/uxc.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/dingtalk-openapi-skill .agents/skills/dingtalk-openapi-skill && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "dingtalk-openapi-skill" agent skill from https://github.com/holon-run/uxc/tree/main/skills/dingtalk-openapi-skill into .agents/skills/dingtalk-openapi-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dingtalk-openapi-skill", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add holon-run/uxc --skill dingtalk-openapi-skill -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install holon-run/uxc dingtalk-openapi-skill --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/holon-run/uxc.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/dingtalk-openapi-skill .cursor/skills/dingtalk-openapi-skill && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "dingtalk-openapi-skill" agent skill from https://github.com/holon-run/uxc/tree/main/skills/dingtalk-openapi-skill into .cursor/skills/dingtalk-openapi-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dingtalk-openapi-skill", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/holon-run/uxc.git --path skills/dingtalk-openapi-skill

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add holon-run/uxc --skill dingtalk-openapi-skill -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install holon-run/uxc dingtalk-openapi-skill --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/holon-run/uxc.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/dingtalk-openapi-skill .gemini/skills/dingtalk-openapi-skill && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "dingtalk-openapi-skill" agent skill from https://github.com/holon-run/uxc/tree/main/skills/dingtalk-openapi-skill into .gemini/skills/dingtalk-openapi-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dingtalk-openapi-skill", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install holon-run/uxc dingtalk-openapi-skill

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add holon-run/uxc --skill dingtalk-openapi-skill -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/holon-run/uxc.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/dingtalk-openapi-skill .github/skills/dingtalk-openapi-skill && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "dingtalk-openapi-skill" agent skill from https://github.com/holon-run/uxc/tree/main/skills/dingtalk-openapi-skill into .github/skills/dingtalk-openapi-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dingtalk-openapi-skill", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add holon-run/uxc --skill dingtalk-openapi-skill -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install holon-run/uxc dingtalk-openapi-skill --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/holon-run/uxc.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/dingtalk-openapi-skill .opencode/skills/dingtalk-openapi-skill && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "dingtalk-openapi-skill" agent skill from https://github.com/holon-run/uxc/tree/main/skills/dingtalk-openapi-skill into .opencode/skills/dingtalk-openapi-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dingtalk-openapi-skill", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: dingtalk-openapi-skill
GitHub stars: 115
Token cost: ~1.6k tokens
SKILL.md length: 513 words
Files: 5 (incl. scripts, references)
Skills in repo: 62
Repo updated: Sep 15, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Operate DingTalk messaging APIs through UXC with a curated OpenAPI schema, app-token bearer auth, and robot/service-group guardrails.

Works in 4 steps: Use the fixed link command by default → Inspect operation schema first → Prefer read/setup validation before writes → …
Tasks that involve OpenAPI specifications
SKILL.md covers Prerequisites, Scope, Subscribe / Stream Mode Status and API Surface Choice, plus 5 more sections
Runs Shell scripts from its folder; calls curl; reaches api.dingtalk.com; needs DINGTALK_APP_KEY and DINGTALK_APP_SECRET

What it does

Dingtalk Openapi Skill is an agent skill from holon-run/uxc. Operate DingTalk messaging APIs through UXC with a curated OpenAPI schema, app-token bearer auth, and robot/service-group guardrails.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/dingtalk-messaging.openapi.json` and `references/usage-patterns.md`).

It sits in Backend & APIs, covering OpenAPI specifications and LLM guardrails. It works with OpenAPI. The repository describes itself as: A unified CLI for discovering and invoking tools across OpenAPI, MCP, GraphQL, gRPC, and JSON-RPC. The licence is MIT.

When your agent uses it

Tasks that involve OpenAPI specifications
Tasks that involve LLM guardrails

Example prompts

“/dingtalk-openapi-skill”

Requirements

A Bash shell
A credential in DINGTALK_APP_KEY
A credential in DINGTALK_APP_SECRET

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Use the fixed link command by default
Inspect operation schema first
Prefer read/setup validation before writes
Execute with key/value or positional JSON

What it can do on your machine

Read from SKILL.md and the folder at commit 562d47c. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
- curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- api.dingtalk.com
Also links to:
- open.dingtalk.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- DINGTALK_APP_KEY
- DINGTALK_APP_SECRET
- DINGTALK_ACCESS_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dingtalk Openapi Skill loads about 1.6k tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 39 tokens; SKILL.md has 513 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~39
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~3.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from holon-run/uxc at commit 562d47c, republished under its MIT licence (© holon-run). 513 words, ~1,560 tokens.

Download SKILL.mdSave it as .claude/skills/dingtalk-openapi-skill/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.

name: dingtalk-openapi-skill
description: Operate DingTalk messaging APIs through UXC with a curated OpenAPI schema, app-token bearer auth, and robot/service-group guardrails.

DingTalk Messaging Skill

Use this skill to run DingTalk messaging operations through uxc + OpenAPI.

Reuse the uxc skill for shared execution, auth, and error-handling guidance.

Prerequisites

uxc is installed and available in PATH.
Network access to https://api.dingtalk.com/v1.0.
Access to the curated OpenAPI schema URL:
- https://raw.githubusercontent.com/holon-run/uxc/main/skills/dingtalk-openapi-skill/references/dingtalk-messaging.openapi.json
A DingTalk internal app or app suite with bot messaging permissions enabled.
A DingTalk app appKey + appSecret, or a current accessToken if you are using the manual fallback path.
Robot code, conversation identifiers, and user identifiers for the target send flows.

Scope

This skill covers a narrow IM-focused request/response surface:

one-to-one bot sends
group bot sends
service group sends
minimal user lookup by unionId

This skill does not cover:

approval, attendance, admin, or broader enterprise app workflows
old oapi.dingtalk.com endpoints
custom robot webhook token/signature flows
inbound callback or webhook receiver runtime

DingTalk has event-delivery flows such as Stream Mode, but those flows are outside the current scope of this skill.

Current uxc subscribe status:

this skill is validated only for request/response messaging operations
DingTalk inbound event/message intake is not currently validated through uxc subscribe

Treat DingTalk as a possible future subscribe target via Stream Mode rather than a currently supported IM subscribe provider.

API Surface Choice

This skill is intentionally pinned to the newer DingTalk Open Platform host:

https://api.dingtalk.com/v1.0

The older oapi.dingtalk.com surface is intentionally excluded from v1 to keep auth and schema shape consistent.

Authentication

DingTalk v1 APIs use app accessToken credentials.

Preferred setup is to store appKey + appSecret as credential fields and let uxc auth bootstrap fetch and refresh the short-lived access token automatically.

Bootstrap-managed setup:

bash

uxc auth credential set dingtalk-app \
  --auth-type bearer \
  --field app_key=env:DINGTALK_APP_KEY \
  --field app_secret=env:DINGTALK_APP_SECRET

uxc auth bootstrap set dingtalk-app \
  --token-endpoint https://api.dingtalk.com/v1.0/oauth2/accessToken \
  --header 'Content-Type=application/json' \
  --request-json '{"appKey":"{{field:app_key}}","appSecret":"{{field:app_secret}}"}' \
  --access-token-pointer /accessToken \
  --expires-in-pointer /expireIn

uxc auth binding add \
  --id dingtalk-app \
  --host api.dingtalk.com \
  --path-prefix /v1.0 \
  --scheme https \
  --credential dingtalk-app \
  --priority 100

Manual fallback if you already have an app access token:

bash

curl -sS https://api.dingtalk.com/v1.0/oauth2/accessToken \
  -H 'Content-Type: application/json' \
  -d '{"appKey":"dingxxxx","appSecret":"xxxx"}'

Configure one bearer credential and bind it to the DingTalk API host:

bash

uxc auth credential set dingtalk-app \
  --auth-type bearer \
  --secret-env DINGTALK_ACCESS_TOKEN

uxc auth binding add \
  --id dingtalk-app \
  --host api.dingtalk.com \
  --path-prefix /v1.0 \
  --scheme https \
  --credential dingtalk-app \
  --priority 100

Validate the active mapping when auth looks wrong:

bash

uxc auth binding match https://api.dingtalk.com/v1.0

Show full SKILL.md (216 more words)Show less

Core Workflow

Use the fixed link command by default:
- command -v dingtalk-openapi-cli
- If missing, create it: uxc link dingtalk-openapi-cli https://api.dingtalk.com/v1.0 --schema-url https://raw.githubusercontent.com/holon-run/uxc/main/skills/dingtalk-openapi-skill/references/dingtalk-messaging.openapi.json
- dingtalk-openapi-cli -h
Inspect operation schema first:
- dingtalk-openapi-cli get:/contact/users/{unionId} -h
- dingtalk-openapi-cli post:/robot/oToMessages/batchSend -h
- dingtalk-openapi-cli post:/robot/groupMessages/send -h
Prefer read/setup validation before writes:
- dingtalk-openapi-cli get:/contact/users/{unionId} unionId=$DINGTALK_UNION_ID
- dingtalk-openapi-cli post:/robot/oToMessages/batchSend -h
- dingtalk-openapi-cli post:/serviceGroup/messages/send -h
Execute with key/value or positional JSON:
- key/value: dingtalk-openapi-cli get:/contact/users/{unionId} unionId=$DINGTALK_UNION_ID language=zh_CN
- positional JSON: dingtalk-openapi-cli post:/robot/groupMessages/send '{"openConversationId":"cidxxxx","robotCode":"dingxxxx","msgKey":"sampleText","msgParam":"{\"content\":\"Hello from UXC\"}"}'

Operation Groups

User Lookup

get:/contact/users/{unionId}

Messaging

post:/robot/oToMessages/batchSend
post:/robot/groupMessages/send
post:/serviceGroup/messages/send

Guardrails

Keep automation on the JSON output envelope; do not use --text.
Parse stable fields first: ok, kind, protocol, data, error.
Prefer uxc auth bootstrap over manual token management. Manual accessToken setup is still supported as a fallback.
All three send operations are high-risk writes. Require explicit user confirmation before execution.
DingTalk msgParam is a JSON-encoded string payload, not a nested JSON object. Build and validate that string carefully before sending.
robotCode, openConversationId, coolAppCode, and target identifiers are all provider-specific routing fields. Missing any of them generally means the send will fail even if auth is valid.
This v1 wrapper does not include custom robot webhook token/sign flows; use app-based APIs only.
dingtalk-openapi-cli <operation> ... is equivalent to uxc https://api.dingtalk.com/v1.0 --schema-url <dingtalk_openapi_schema> <operation> ....

References

Usage patterns: references/usage-patterns.md
Curated OpenAPI schema: references/dingtalk-messaging.openapi.json
DingTalk developer docs: https://open.dingtalk.com/document/

Files

SKILL.md and 4 other files (scripts, references) in skills/dingtalk-openapi-skill of holon-run/uxc.

SKILL.md
agents/openai.yaml
references/dingtalk-messaging.openapi.json
references/usage-patterns.md
scripts/validate.sh

Open the folder on GitHubat commit 562d47c

Compare with similar skills

Dingtalk Openapi Skill next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dingtalk Openapi Skill compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Dingtalk Openapi Skill this skillholon-run/uxc	115	—	~1.6k	Automated safety check: Pass	MIT	22 days ago
Aliyun Green Moderationcinience/alicloud-skills	397	—	~728	Automated safety check: Pass	MIT	1 mo ago
ToolJet Marketplace Plugin BuilderToolJet/ToolJet	41k	—	~2.1k	Automated safety check: Pass	AGPL-3.0	yesterday
Step Partsearthtojake/text-to-cad	18k	1 repos	~1.5k	Automated safety check: Pass	MIT	yesterday
API DesignerJeffallan/claude-skills	12k	2 repos	~2k	Automated safety check: Pass	MIT	4 days ago
OpenAPI to MCP Servermcp-use/mcp-use	11k	—	~5.2k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Aliyun Green Moderation
cinience/alicloud-skills
A skill your agent uses when managing Alibaba Cloud Content Moderation (Green) via OpenAPI/SDK, including the user needs content moderation resource and policy operations, including…
397 GitHub stars~728 tokensUpdated 1 mo ago
Backend & APIsAuto-check passed
ToolJet Marketplace Plugin Builder
ToolJet/ToolJet
Turns an API description, such as an OpenAPI file or a Postman collection, into a connector plugin for ToolJet's marketplace and checks it with the repo's validator.
41k GitHub stars~2.1k tokensUpdated yesterday
Backend & APIsAuto-check passed
Step Parts
earthtojake/text-to-cad
Find, evaluate, and download common purchasable CAD parts from step.parts, including named off-the-shelf actuators, servos, motors, electronics boards, connectors, screws, bolts, nuts, washers…
18k GitHub starsUsed in 1 repo~1.5k tokens
Backend & APIsAuto-check passed
API Designer
Jeffallan/claude-skills
Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.
12k GitHub starsUsed in 2 repos~2k tokens
Backend & APIsAuto-check passed
OpenAPI to MCP Server
mcp-use/mcp-use
Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.
11k GitHub stars~5.2k tokensUpdated yesterday
Backend & APIsAuto-check passed
Use Yaak
mountain-loop/yaak
A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…
19k GitHub stars~1.9k tokensUpdated today
Backend & APIsAuto-check passed

Questions about Dingtalk Openapi Skill

What does Dingtalk Openapi Skill do?

Operate DingTalk messaging APIs through UXC with a curated OpenAPI schema, app-token bearer auth, and robot/service-group guardrails. Dingtalk Openapi Skill is an agent skill from holon-run/uxc. Operate DingTalk messaging APIs through UXC with a curated OpenAPI schema, app-token bearer auth, and robot/service-group guardrails.

When should I use Dingtalk Openapi Skill?

Dingtalk Openapi Skill fits situations like: tasks that involve OpenAPI specifications; tasks that involve LLM guardrails.

How do I install Dingtalk Openapi Skill in Claude Code?

Run `npx skills add holon-run/uxc --skill dingtalk-openapi-skill -a claude-code`. Or copy the skill folder (skills/dingtalk-openapi-skill in holon-run/uxc) into .claude/skills/dingtalk-openapi-skill in your project. Claude Code loads it when a task matches its description.

How do I install Dingtalk Openapi Skill in Codex?

Run `npx skills add holon-run/uxc --skill dingtalk-openapi-skill -a codex`. Or copy the skill folder (skills/dingtalk-openapi-skill in holon-run/uxc) into .agents/skills/dingtalk-openapi-skill in your project. Codex loads it when a task matches its description.

Can I use Dingtalk Openapi Skill in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add holon-run/uxc --skill dingtalk-openapi-skill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dingtalk-openapi-skill, .gemini/skills/dingtalk-openapi-skill, .github/skills/dingtalk-openapi-skill and .opencode/skills/dingtalk-openapi-skill in your project.

What does Dingtalk Openapi Skill need to run?

Going by SKILL.md and its folder, Dingtalk Openapi Skill needs a shell for the scripts in its folder, the command-line tools its instructions call (curl) and credentials named DINGTALK_APP_KEY, DINGTALK_APP_SECRET and DINGTALK_ACCESS_TOKEN. Our summary lists: A Bash shell; A credential in DINGTALK_APP_KEY; A credential in DINGTALK_APP_SECRET.

Does Dingtalk Openapi Skill access the network?

SKILL.md names 2 domains. In commands or code: api.dingtalk.com; the agent is likely to contact it when it follows the instructions. As links in the text: open.dingtalk.com. This is read from the text; nothing was executed.

Is Dingtalk Openapi Skill safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Dingtalk Openapi Skill use?

Dingtalk Openapi Skill is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dingtalk Openapi Skill use?

About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.

What are the alternatives to Dingtalk Openapi Skill?

Skills that share tags, products or a category with Dingtalk Openapi Skill: Aliyun Green Moderation (cinience/alicloud-skills, 397 stars), ToolJet Marketplace Plugin Builder (ToolJet/ToolJet, 41k stars), Step Parts (earthtojake/text-to-cad, 18k stars) and API Designer (Jeffallan/claude-skills, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dingtalk Openapi Skill?

holon-run (a GitHub organization) maintains it in holon-run/uxc, which has 115 GitHub stars. The repository holds 62 skills in this directory. The repository was last updated on September 15, 2026.

Source: holon-run/uxc on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Dingtalk Openapi Skill

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

DingTalk Messaging Skill

Prerequisites

Scope

Subscribe / Stream Mode Status

API Surface Choice

Authentication

Core Workflow

Operation Groups

User Lookup

Messaging

Guardrails

References

Files

Compare with similar skills

Similar skills

More from holon-run/uxc

Related

Questions about Dingtalk Openapi Skill