Name: microsoft-teams
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

microsoft-teams

Microsoft Teams integration. Manage communication data, records, and workflows. Use when the user wants to interact with Microsoft Teams data.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/microsoft-teams/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

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

The body is highly actionable with concrete Membrane CLI commands and a useful action catalog, but it over-explains Teams itself, inlines a large reference table instead of externalizing it, and lacks verification steps for its send/create operations and consistent step numbering.

Suggestions

Remove the 'what is Microsoft Teams' opening sentence and the auth-plumbing marketing phrasing; assume Claude knows the platform.

Move the 20-row Popular actions table into a references file (e.g. references/actions.md) and link to it from the body to improve progressive disclosure.

Add explicit verification after destructive/outward-facing actions (e.g. re-fetch the channel message after send-channel-message to confirm delivery) and fix the dangling 'Step 2' reference by labeling the sequence steps.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete CLI commands, but it opens by explaining what Microsoft Teams is ('a unified communication and collaboration platform...'), includes marketing-style phrasing ('so you can focus on the integration logic rather than auth plumbing'), and inlines a 20-row action reference table that could be tightened or externalized.	3 / 5
Actionability	Provides copy-paste-ready commands for install, login, connection ensure, polling, action list/run with JSON input, and proxy requests, plus a concrete action-key table; the minor gap is that every example uses placeholders (CONNECTION_ID, <actionId>, <id>) with no single fully-worked end-to-end example using real values.	4 / 5
Workflow Clarity	The connect-to-poll-to-run sequence is present with state-machine checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but the numbering is inconsistent ('skip to Step 2' with no labeled Step 2) and the destructive/outward-facing actions (send message, create team/channel) have no verification steps, which caps this dimension at 3 per the batch/destructive guideline.	3 / 5
Progressive Disclosure	Sections are organized with clear headers, but the large Popular actions catalog is inlined in a single ~175-line SKILL.md with no bundle/reference files at all, matching the anchor of some structure with content that should be separate kept inline.	3 / 5
	Total	13 / 20 Passed

Description

66%Weight 40%Scale 1-5

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

The description cleanly states a distinct Microsoft Teams niche with an explicit 'Use when' trigger, but its capability list ('manage communication data, records, and workflows') is generic and it omits common natural terms like 'Teams', 'chat', 'meetings', and 'channels'.

Suggestions

Replace the generic verb 'Manage' with concrete Microsoft Teams actions such as 'List and send channel messages, create chats, teams, and channels, and manage meetings'.

Add natural trigger terms users would actually say, e.g. 'Use when the user mentions Teams chats, channel messages, meetings, or wants to send/read Microsoft Teams messages'.

Reflect the breadth of the skill body (20+ actions) in the description so the 'what' is comprehensive rather than abstract.

Dimension	Reasoning	Score
Specificity	Names the domain ('Microsoft Teams integration') and enumerates action areas ('Manage communication data, records, and workflows'), but the actions are generic ('manage') rather than concrete like send/read/list, so it sits at the anchor listing domain plus a few actions without being comprehensive.	3 / 5
Completeness	Both 'what' ('Manage communication data, records, and workflows') and an explicit 'when' ('Use when the user wants to interact with Microsoft Teams data') are present; the 'when' is explicit but the 'what' is generic rather than fully concrete, so it does not reach the top anchor.	4 / 5
Trigger Term Quality	'Microsoft Teams' and 'communication data' are relevant keywords, but common natural variations users would say — 'Teams', 'chat', 'messages', 'meetings', 'channels' — are missing, matching the anchor of some relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	'Microsoft Teams integration' with a 'Microsoft Teams data' trigger is a clear, specific platform niche with minimal overlap risk against other skills, matching the top anchor.	5 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/microsoft-teams/SKILL.md
Commit: f484c82

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.