Index of every page on this site: llms.txt
All skills
ccheney avatar

/teams-message-formatting

@0eea7b0
Run it yourself

Format or debug Microsoft Teams bot text, Adaptive Card text, and Graph chatMessage bodies. Use for markup, mentions, links, escaping, or client rendering issues; not card layout/actions or ordinary Teams conversation retrieval.

Use this Skill: https://skilld.dev/gh/ccheney/robust-skills/teams-message-formatting

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈64 tokens for metadata: the name and description. ≈698 when used: this file. ≈5.9k more on demand in 5 files.

Description uses 3.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈255 characters, or 3.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Surface Text format Mention metadata
Bot activity text Bot Markdown or textFormat: "xml" subset Activity entities
Adaptive Card TextBlock / facts Limited Markdown, no HTML Root msteams.entities
Graph chatMessage.body text or Teams-restricted html Body <at id="N"> plus matching mentions entry
Hero/thumbnail card text XML/HTML subset Surface-specific; titles/subtitles are unformatted

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.

Task Reference
Bot Markdown/XML, card Markdown, hero cards, legacy text MARKDOWN-HTML.md
Bot/card/Graph mentions; users, tags, teams, channels MENTIONS.md
Graph HTML, code/emoji tags, attachments, permissions GRAPH-CHATMESSAGE.md
Compact surface and syntax lookup CHEATSHEET.md

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill is a purely informational and educational guide for developers to correctly format messages for Microsoft Teams. It provides detailed documentation on different markup systems (Markdown, HTML, XML, Adaptive Cards) and includes safety best practices such as escaping user content to prevent rendering issues. No security risks were detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 0eea7b0. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 2 months ago

README badge

README badge for ccheney/robust-skills/teams-message-formatting