AGENT SKILL

dingtalk-aicard

Create, edit, and validate DingTalk AI Card (A2UI) JSON files offline. Use for cards built from requirements or images, structural protocol errors, and named component or function contract lookup through native DWS commands. Send a card to the current user only when a preview is requested.

License 许可
Apache-2.0
最近更新
2026-11-06
Stars
★ 98
Forks
39

01 前言 Front Matter

name
dingtalk-aicard
version
1.0.66.1
disabled
true
metadata
{ "cliHelp": "dws aicard --help", "category": "product", "requires": { "bins": [ "dws" ] }, "catalogId": "https://dingtalk.com/card/a2ui/catalogs/public/catalog.json", "cli_version": ">=0.2.14", "aicardVersion": "V0.8", "protocolVersion": "1.0" }
description
Create, edit, and validate DingTalk AI Card (A2UI) JSON files offline. Use for cards built from requirements or images, structural protocol errors, and named component or function contract lookup through native DWS commands. Send a card to the current user only when a preview is requested.
connector_id
dws
install_source
connector

02 资源文件 31

03 SKILL.md 正文

DingTalk AI Cards V0.8

Create or edit an A2UI file from the user's content or image, look up only the contracts needed, and distinguish local validation from delivery and client rendering. This Skill uses the DingTalk V0.8 package based on A2UI 1.0: message version is "v1.0" and send API protocolVersion is "1.0".

Follow the user's requested lookup, file, send or update directly; the references are not a mandatory sequence. Obey command and protocol requirements. Ask only when missing facts, interaction meaning or the target affect the outcome.

Route by intent

Read only the relevant reference. Do not preload the complete protocol, every pattern, or the whole guide.

Intent First reference Optional follow-up
Set up lookup and validation Execution environment Installed command help
Create or redesign from content or images Visual focus and layout One relevant pattern or example
Query a known name Query a named contract The result's source pointer
Find an unknown name Component, function, or Token index Query only the selected names
Construct or repair a card Construct and validate Diagnostic pointer and named contract
Send, preview, or update Delivery boundary Installed command help

Use patterns for composition guidance and linked JSON for message shapes. Read a named example directly; use the example index only to choose one.

Composition patterns

Content Reference
Notifications and reminders Notification
Object facts and decisions Detail
Illustrated content and attachments Content
Metrics and reports Report
Editable inputs and submission Form
Generation and execution updates Progress

For editable inputs, also consult the form pattern for bindings and submission, even when another pattern describes the card. When replaying an execution example, read Examples and replay for its batch boundaries, even if the JSON was selected directly.

Execution environment

This edition uses native DWS commands, not Python. Confirm dws aicard --help exposes explain, lint, and preview; copying the Skill does not install commands. Lookup and lint are offline and need no Profile. Check each command's current help and structured envelope (ok, outcome, data, or error.details). If unavailable, references can guide a draft, but do not claim DWS validation.

Query a named contract

dws aicard explain Tabs --format json
dws aicard explain Text Row Column --compact --format json

Query only needed names. Compact $contractRef and definitions are lookup metadata, not A2UI fields. Query without --compact for expanded fields; source locates omitted details.

Construct and validate

Use references/protocol/ as the contract. Write an ordered JSON message array. Within one card, keep the same surfaceId; choose an ID suitable for that card when creating it. A complete new card requires Surface creation, root data initialization (even {} for static content), and a component with ID root. The recommended explicit form is:

[
  {"version":"v1.0","createSurface":{"surfaceId":"example-surface","catalogId":"https://dingtalk.com/card/a2ui/catalogs/public/catalog.json"}},
  {"version":"v1.0","updateDataModel":{"surfaceId":"example-surface","path":"/","value":{}}},
  {"version":"v1.0","updateComponents":{"surfaceId":"example-surface","components":[{"id":"root","component":"Text","text":"Example"}]}}
]

This is a structural example, not a business card to send. Protocol-valid inline initialization in createSurface.dataModel and createSurface.components is also accepted; three separate messages are not the only valid representation.

Scenario Messages and checks
Complete new card Create and initialize as above; use --preflight new-card
Host-created empty Surface Initialize its existing ID without createSurface; use Schema and resource checks
Existing card update Keep IDs and send only intentional changes; use Schema and resource checks, then check against known current state

Removing createSurface from a complete file does not make it a safe delta. Do not replay form defaults or unrelated initial data: that can overwrite user input. Resource checks alone cannot prove an update preserves state or references.

Preserve unrelated styling when editing. For ordinary new cards, prefer a root Column without background fields. If a root Card is needed, use backgroundColor: "#00FFFFFF" and no background token. Honor explicit surface designs; see design guidance.

Prefer Markdown for rich text and static tables; Text for short titles and labels. Omit root padding for ordinary cards. Do not default to CardHeader; preserve it when requested and check insets.

Preserve supplied facts and requested interactions; label demonstration data. Replace REPLACE_* placeholders before delivery. Do not present unverified resources, unconnected actions, or simulated states as real and working.

Choose literals or bindings as the field contract permits. Initialize bound data with the required types and update it through updateDataModel; change component literals through updateComponents. sendDataModel controls whether A2A messages include the full data model, not whether bindings work.

dws aicard lint --file card.a2ui.json --format json

Choose --preflight new-card or --preflight resources for the selected scenario, and use --emit only when serialized message strings are needed; it cannot be combined with --fragment. Check exit status and data.valid plus data.preflight.valid when selected. dws aicard lint --self-check --format json verifies the full package.

Validation scope

Lint checks syntax and Schema fields. New-card preflight additionally checks initialization, root, duplicate IDs within a message, static references and cycles in the final component snapshot, not every intermediate streaming frame. Unreachable components are warnings. Resource preflight checks inline encoding; neither mode evaluates bindings or proves image loading. --fragment checks component/message fragments; it is not a way to bypass new-card initialization. Do not silently rewrite user data, remove requested components, or downgrade interactions to pass a check.

A successful named lookup is not a full package check. Use the self-check supported by the selected execution environment; local checks do not establish client behavior.

Delivery boundary

With native --emit, read data.a2uiMessages.

Send only when requested. Resolve exactly one target under the sending profile: --conversation-id for a conversation or --open-dingtalk-id for a person. Names are not target IDs. Inspect installed command help, JSON-encode the emitted message-string array as one --content argument, and call dws chat message send-a2ui-card. Preserve the request, target, profile and returned bizId. An uncertain result must be checked before another create; do not resend automatically.

Creation starts in PROCESSING. Update with dws chat message update-a2ui-card --biz-id <bizId> --content <message-strings> --flow-status <state> under the original profile. Keep the same surfaceId and component IDs; send only intended updateDataModel or updateComponents changes, not another createSurface or unrelated defaults. Static cards require --flow-status FINISH with a nonempty valid delta; prepare it before sending and preserve business data. Stream complete messages, not JSON tokens. Resource preflight checks only the delta. If current state is known, validate it with the delta; Schema validity does not prove business safety.

dws aicard preview --file card.a2ui.json sends a self-preview in PROCESSING; --dry-run does not send. For a completed static preview, finish it under the same profile with dws chat message update-a2ui-card --biz-id <data.bizId> --content <message-strings> --flow-status FINISH, using a nonempty state-preserving delta for the same Surface. Do not replay form defaults. Use server-issued data.bizId, never request-side bizCardId. If absent, inspect updateWarning and the receipt; do not recreate automatically. openTaskId cannot be used with query-send-status.

After sending, use the available readback capability under the same profile and target to identify this exact card from returned instance/message identifiers. Generic card text and a nearby timestamp are not sufficient. Report request acceptance, same-target readback, client rendering and interaction separately. If readback is unavailable or inconclusive, mark it unverified; do not claim the user received or correctly rendered the card from API acceptance alone.

Report the file, checks actually run, and delivery result when requested. Local validation and request acceptance do not prove client rendering.

04 同仓库更多 Skills

ahang1598
ahang1598/doubao-workbuddy-qwenwork-skills

xiaoyi-pdf-win

PDF 综合处理技能,处理文档生成、编辑、安全与解析。 适用情形: 1. 创建与排版:从零生成报告、提案、简历等 PDF,或对现有文档重新排版美化; 2. 表单与水印:自动填写 PDF 表单字段,或添加文字/图片水印(如打水印、标机密); 3. 页面管理:合并多个 PDF,或拆分、提取指定页码; 4. 安全控制:为 PDF 添加密码(加密)或移除密码(解密); 5. 内容提取:从 PDF 中提取纯文本或导出表格数据。 只要用户诉求涉及生成、排版、美化、转换、拼接、拆分 PDF,或处理水印、表单、密码,必须触发本技能。

★ 98
ahang1598
ahang1598/doubao-workbuddy-qwenwork-skills

skill-creator-win

Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.

★ 98
ahang1598
ahang1598/doubao-workbuddy-qwenwork-skills

markitdown-win

Convert files and office documents to Markdown. Supports PDF, DOCX, PPTX, XLSX, images (with OCR), audio (with transcription), HTML, CSV, JSON, XML, ZIP, YouTube URLs, EPubs and more.

★ 98
ahang1598
ahang1598/doubao-workbuddy-qwenwork-skills

minimax-docx

Professional DOCX document creation, editing, and formatting using OpenXML SDK (.NET). Three pipelines: (A) create new documents from scratch, (B) fill/edit content in existing documents, (C) apply template formatting with XSD validation gate-check. MUST use this skill whenever the user wants to produce, modify, or format a Word document — including when they say "write a report", "draft a proposal", "make a contract", "fill in this form", "reformat to match this template", or any task whose final output is a .docx file. Even if the user doesn't mention "docx" explicitly, if the task implies a printable/formal document, use this skill.

★ 98
ahang1598
ahang1598/doubao-workbuddy-qwenwork-skills

skillhub-daily

SkillHub 每日推荐 - 扫描 skillhub.cn 全站 Top100 + 7 大分类各 Top20(共 240 个 Skill), 基于用户痛点精准推荐高价值 Skill,支持 IMA/飞书/Obsidian 多通道存储。 触发词:每日推荐、SkillHub 日报、潜力Skill、帮我推荐技能。 支持两种使用模式:常规 Skills 模式(对话触发)/ Cron 定时任务模式。

★ 98
ahang1598
ahang1598/doubao-workbuddy-qwenwork-skills

deep-research

Structured deep research workflow with human-in-the-loop control. Use /research to generate research outline, /research-deep for parallel web search across items, /research-report to compile markdown reports. Supports academic research, benchmark research, technology selection, market analysis, and due diligence. Triggers: 'deep research', 'research topic', 'benchmark comparison', 'technology survey', 'market analysis'. Requires: WebSearch capability.

★ 98