mcpField
T
teams-adaptive-cards

teams-adaptive-cards

github.com/ccheneyDevelopment6149 installsUpdated 7w ago
Repository

About teams-adaptive-cards

A skill for creating Microsoft Teams Adaptive Cards that match the requested transport and client capabilities. It guides card structure, feature selection, validation, and delivery without assuming an unprovided backend or recipient.

Key features

  1. 01Choose the correct transport wrapper
  2. 02Match elements to client support
  3. 03Use bundled implementation references
  4. 04Validate payloads with a Node.js script
  5. 05Check delivery without posting

Use cases

  1. 01Create cards for Teams bots or workflows
  2. 02Prepare Graph chatMessage attachments
  3. 03Build card forms and notifications
  4. 04Check payloads before delivery

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ccheney/robust-skills --skill teams-adaptive-cards

After installing, type/teams-adaptive-cardsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
references/
ACTIONS.md
CHEATSHEET.md
ELEMENTS.md
GRAPH-ATTACHMENTS.md
RESPONSIVE-DESIGN.md
SURFACES.md
WEBHOOKS-WORKFLOWS.md
scripts/
check-teams-card.mjs

Details

From the project README

Teams Adaptive Cards

Build the requested card for its actual Teams transport and client capabilities. The user's explicit instructions take precedence over this skill's guidelines.

Select the transport

Use the requested content/actions, delivery code or payload, and target clients as input. A card's JSON and its delivery wrapper are separate contracts.

TransportRequired shape
Bot / Teams SDKActivity attachments[], card content as an object
Workflows webhook{ "type": "message", "attachments": [...] }
Graph chatMessageHTML attachment placeholder with matching ID; attachment content as a JSON string
Message extensionAttachment and preview appropriate to the extension type

If delivery is unspecified, a raw card can be prepared while clarifying the transport. Do not invent a webhook URL, recipient, or bot backend. An approval/form needs a transport that handles its actions; a notification webhook is not a bot.

Match capabilities

The references use a Teams baseline of card versions through 1.5, with 1.2 as a conservative mobile fallback. Select the minimum version needed by the requested elements and verify current host support when newer features matter. A schema version alone does not guarantee a Teams client renders an element.

Use card elements for layout: TextBlock, FactSet, Table, inputs, and actions as appropriate. TextBlock Markdown is limited; HTML, Markdown tables, and code fences are not substitutes for supported card elements. Provide wrapping, meaningful fallback text, and consistent mention metadata.

References

Load only the transport, element, or interaction needed.

TaskReference
Delivery path, bots, message extensionsSURFACES.md
Inputs, tables, code, charts, people pickerELEMENTS.md
Submit/Execute, refresh, user-specific viewsACTIONS.md
Webhook notifications or requested connector migrationWEBHOOKS-WORKFLOWS.md
Graph attachment IDs, encoding, permissionsGRAPH-ATTACHMENTS.md
Width, mobile layout, accessibilityRESPONSIVE-DESIGN.md
Compact wrapper/version/limit lookupCHEATSHEET.md

Validate and deliver

For generated or changed payload files, run scripts/check-teams-card.mjs with Node.js. Resolve the script relative to this skill's directory, not the user's working directory:

node /path/to/teams-adaptive-cards/scripts/check-teams-card.mjs --target webhook /path/to/payload.json

Targets: auto, card, bot, webhook, graph. Exit 0 means no errors (warnings can remain), 1 means errors/invalid JSON, and 2 means invalid CLI usage. Interpret warnings against the requested client/transport; the linter is a local check, not proof of live rendering. If Node is unavailable, inspect the wrapper and fields and state that the linter was not run.

Deliver the requested JSON or integration fix and verification outcome. Test live delivery only when requested or already authorized; payload creation does not require posting. Consult Teams card documentation for host capabilities not established by the bundled references.

Comments

Markdown supported