ccheney/robust-skills/teams-message-formatting

Teams Message Formatting

Format supplied text for the Teams surface that receives it. The user's explicit instructions take precedence over this skill's guidelines.

Identify the text system

Use the content, destination field, and existing payload or SDK as input. Infer the text system from that context; ask for the destination when the missing choice changes syntax or mention metadata.

Slack mrkdwn is not Teams markup. Adaptive Card Markdown does not support headings, tables, images, code fences, or blockquotes; use supported card elements when those structures are requested. Text-only content does not require a card.

Preserve text and identity

• Escape for the receiving syntax, then serialize JSON. Do not concatenate unescaped user text into HTML/XML or mention markup.
• Keep visible mention text and its metadata synchronized. Use supplied or resolved IDs; display names are not identity evidence.
• Respect client differences, such as bot-list support on mobile. Do not change a transport just to fix punctuation.
• For a Graph payload, distinguish ordinary delegated sends from migration permissions. An app-only notification requires a supported delivery path; explain a missing capability without pretending the payload creates it.

Return the requested text, corrected string/object, or integration patch, preserving meaning and the known surface. Identify any missing runtime IDs or unverified client behavior. Posting is separate from formatting and requires the user's request or existing authorization.

References

Load the relevant format or metadata details only.

For card layout/actions, use teams-adaptive-cards if installed or the Teams card documentation. This text-formatting workflow does not depend on another skill being installed.