CtrlK
BlogDocsLog inGet started
Tessl Logo

teams

Search through Microsoft Teams chats or channels, triage unread or recent activity, draft follow-ups, and manage Planner tasks through connected Teams data.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 concise, highly actionable, well-sequenced instruction skill with explicit validation and error-recovery loops; its main gap is the absence of progressive disclosure to offload detail into reference files.

DimensionReasoningScore

Conciseness

Lean, instruction-dense body focused on connector-specific gotchas Claude would not already know; no padding explaining what Teams is, and every line earns its place.

3 / 3

Actionability

Provides concrete, specific guidance with exact tool calls and parameters (e.g., list_channel_messages(top=50), create_chat(chat_type='oneOnOne')) and explicit fallback paths, which is actionable for an instruction skill.

3 / 3

Workflow Clarity

Sequences are explicit with verification checkpoints (support/capability checks before concluding unsupported) and feedback loops for write failures (DM-creation fallback, write-failure blocker classification).

3 / 3

Progressive Disclosure

Well-organized sections, but at ~70 lines the content is entirely inline with no progressive disclosure to separate reference files; the only bundle assets are unreferenced SVG icons.

2 / 3

Total

11

/

12

Passed

Description

75%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-triggered Teams description with concrete actions and natural terms, but it omits an explicit 'Use when...' trigger and overlaps with sibling Teams skills on triage and drafting.

Suggestions

Add an explicit 'Use when...' clause stating when to invoke this skill (e.g., "Use when triaging or summarizing Teams activity and managing Planner follow-ups").

Narrow the triage/drafting claims to reduce overlap with sibling skills like teams-notification-triage and teams-reply-drafting, or explicitly position this skill as the router.

Add a trigger keyword variation (e.g., 'Microsoft Teams messages', 'Planner tasks from Teams') to broaden natural-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Search through Microsoft Teams chats or channels", "triage unread or recent activity", "draft follow-ups", "manage Planner tasks" — matching the multi-action anchor.

3 / 3

Completeness

Clearly states what the skill does but lacks an explicit "Use when..." trigger clause, so per the guideline completeness is capped at 2 even though the "when" is somewhat implied.

2 / 3

Trigger Term Quality

Uses natural user-facing terms ("chats or channels", "unread or recent activity", "follow-ups", "Planner tasks") that a user would plausibly say, with good coverage of variations.

3 / 3

Distinctiveness Conflict Risk

Teams/Planner niche is specific, but the description claims triage and drafting follow-ups, which overlap with dedicated sibling skills (notification triage, reply drafting), creating moderate conflict risk.

2 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 7 suspicious

Warning

Total

15

/

16

Passed

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.