CtrlK
BlogDocsLog inGet started
Tessl Logo

teams-messages

Compose, route, draft, or send Microsoft Teams messages with exact destination resolution, real user mentions, and Teams-native DM or channel routing.

74

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-organized instruction-only skill that names exact tools and parameters, sequences the workflow with a validation checkpoint and fallback paths, and stays within a single clear purpose.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanations of what Teams, DMs, or mentions are; every section is tight, actionable bullet guidance with no padding, matching the lean/efficient anchor.

3 / 3

Actionability

Names exact tools and parameters for each routing case (resolve_team, resolve_channel, resolve_chat, resolve_user, send_chat_message, create_chat(chat_type='oneOnOne'), send_channel_message, reply_to_message, create_channel), which is concrete and actionable for an instruction-only skill; absence of code is not penalized per the scoring notes.

3 / 3

Workflow Clarity

The Workflow is a clear 5-step sequence with an explicit validation checkpoint (validate_write_target) and concrete error-recovery fallbacks (group-chat fallback on caller-membership mismatch, returning draft text when a user cannot be resolved), satisfying the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

This is a compact (under 50 lines), single-purpose skill with no bundle files, organized into well-signaled sections (Overview, Workflow, Mention Rules, Routing Rules, Support Boundaries, Output Conventions), which per the simple_skills note can score 3 without external file references.

3 / 3

Total

12

/

12

Passed

Description

82%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-differentiated description with strong concrete actions and natural trigger terms, but it omits any explicit 'Use when...' clause, which caps completeness at 2.

Suggestions

Add an explicit 'Use when...' clause naming common trigger phrasings (e.g., 'Use when sending or drafting Teams messages, replying in a thread, @mentioning someone in a DM or channel, or starting a new chat').

Surface natural user phrasings like 'DM me on Teams', 'post in the channel', or 'reply in the thread' so the description matches what users actually say, further strengthening trigger-term quality and completeness.

Mirror the routing cases from the body (existing chat, new DM/group chat, channel thread, reply) as a compact 'when' list so the 'what' and 'when' are both explicit.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Compose, route, draft, or send Microsoft Teams messages') plus specific sub-capabilities ('exact destination resolution, real user mentions, and Teams-native DM or channel routing'), matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

Clearly answers 'what' but provides no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 2 (it does not reach the anchor-3 requirement of explicit 'when' triggers).

2 / 3

Trigger Term Quality

Covers natural terms users would say — 'Microsoft Teams messages', 'send', 'DM', 'channel', 'mention' — giving good coverage rather than only a single relevant keyword; richer than the anchor-2 'Works with PDF files'.

3 / 3

Distinctiveness Conflict Risk

It is narrowly scoped to Microsoft Teams messaging with Teams-native routing and mentions, a clear niche unlikely to trigger for the wrong skill; not merely 'somewhat specific' as in anchor 2.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.