CtrlK
BlogDocsLog inGet started
Tessl Logo

teams-channel-summarization

Summarize activity from one Microsoft Teams channel or one scoped Teams conversation and return a concise recap or post-ready follow-up.

73

Quality

91%

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

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 well-structured, token-efficient instruction skill with concrete tool guidance, a clear conditional workflow, and a pre-flight checklist; content is appropriately inline for a single-purpose skill.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanation of what Teams is or how the APIs work; every section (Start Here, Workflow, Formatting) earns its place with no padding.

3 / 3

Actionability

Concrete, executable guidance throughout: named tool calls with parameters ('resolve_team', 'resolve_channel', 'list_channel_messages(top=50)', 'include_replies=True', 'fetch') plus a copy-ready formatting template.

3 / 3

Workflow Clarity

A clearly sequenced 6-step workflow with explicit conditional branches (if window / if no window / expand replies only when material) and a pre-flight 'Start Here' checklist; the read/summarize task is not destructive or batch, so the 2-cap does not apply.

3 / 3

Progressive Disclosure

A single-purpose skill (~55 lines) with no need for external bundle files, organized into clear sections with one well-signaled one-level reference (the related teams-messages skill in a table); no bundle files exist to verify.

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 concise, specific description with natural trigger terms and a clear niche, but it lacks an explicit 'Use when...' trigger clause, which caps completeness at 2.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to catch up on, summarize, or recap a Teams channel or conversation, or to draft a follow-up from channel activity.'

Include a few more natural trigger variations (e.g. 'what did I miss', 'catch up on') to broaden trigger-term coverage beyond 'summarize', 'recap', and 'follow-up'.

Optionally name the concrete output formats the user can request ('concise recap' vs 'post-ready follow-up') as distinct triggers to sharpen the when-guidance.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Summarize activity from one Microsoft Teams channel' and 'return a concise recap or post-ready follow-up' — matching the anchor for several specific concrete actions rather than vague language.

3 / 3

Completeness

The 'what' is explicit (summarize activity, return a recap or follow-up) but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

Natural terms a user would actually say are present — 'Teams channel', 'conversation', 'recap', 'follow-up' — giving good coverage of phrasings users use when requesting this skill.

3 / 3

Distinctiveness Conflict Risk

The scope is a clear niche — 'one Microsoft Teams channel or one scoped Teams conversation' — distinct from the related teams-messages sending skill, making false triggers unlikely.

3 / 3

Total

11

/

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: 1 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.