microsoft-teams-automation

Automate Microsoft Teams tasks via Rube MCP (Composio): send messages, manage channels, create meetings, handle chats, and search messages. Always search tools first for current schemas.

1.46x

Quality

78%

Does it follow best practices?

Impact

95%

1.46x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/microsoft-teams-automation/SKILL.md

Quality

Content

82%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.

A highly actionable, well-structured body that gives exact tool sequences, parameters, and pitfalls for each Teams workflow, with the main weaknesses being some redundancy between the per-workflow Pitfalls and the 'Known Pitfalls' section and the lack of any progressive split for a ~250-line document.

Suggestions

De-duplicate by folding the 'Known Pitfalls' section into the per-workflow Pitfalls (or vice versa), keeping only cross-cutting items (rate limits, ID formats) in a single consolidated section.

Add an explicit post-action verification step for state-changing workflows (e.g. after POST_CHANNEL_MESSAGE, fetch the message back to confirm delivery) to strengthen feedback loops.

Consider moving the full per-tool parameter catalog and 'Common Patterns' into a separate reference file, leaving SKILL.md as a concise overview that links one level deep.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, task-specific detail (tool slugs, params, error codes) rather than concept explanations Claude already knows, but the 'Known Pitfalls' section and 'Quick Reference' table restate per-workflow pitfalls and tool slugs already covered above, adding moderate redundancy.	4 / 5
Actionability	Concrete, executable guidance throughout: exact tool slugs (MICROSOFT_TEAMS_TEAMS_LIST), parameters with format examples (UUID, '19:...@thread.tacv2', ISO 8601), and specific error codes (403/429/413) with remediation — copy-paste ready for an MCP-tool skill.	5 / 5
Workflow Clarity	Each workflow has a numbered 'Tool sequence' tagged [Required]/[Optional]/[Prerequisite], and Setup includes an explicit validation checkpoint ('Confirm connection status shows ACTIVE before running any workflows') plus a 429 backoff feedback loop, but post-action verification for state-changing ops (post/create/add) is only implicit.	4 / 5
Progressive Disclosure	Well-organized single file with clear section headers and a Quick Reference table for navigation, plus a well-signaled external toolkit-docs link; however, at ~250 lines it is monolithic with no split into one-level-deep reference files, which is a minor organization gap.	4 / 5
	Total	17 / 20 Passed

Description

75%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.

A specific, well-targeted description naming the domain and five concrete actions, but it lacks an explicit 'Use when...' trigger clause, which caps completeness and leaves the activation condition implicit.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to send or search Teams messages, manage channels or chats, or schedule Teams meetings.'

Include a few natural synonyms users might say ('DMs', 'direct messages', 'group chat', 'Teams files') to broaden trigger-term coverage.

Lead with the capability verb in a consistent voice and consider moving 'Always search tools first for current schemas' into the body so the description stays a pure what+when statement.

Dimension	Reasoning	Score
Specificity	Lists five concrete actions ('send messages, manage channels, create meetings, handle chats, and search messages') across the named Microsoft Teams domain, giving comprehensive coverage rather than just 1-2 actions.	5 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'Always search tools first for current schemas' is operational instruction, not a usage trigger, so completeness is capped at 3 per the rubric.	3 / 5
Trigger Term Quality	Good natural keyword coverage ('messages', 'channels', 'meetings', 'chats', 'search messages', 'Microsoft Teams'), but a few natural variations/synonyms (e.g. 'calls', 'files', 'DMs') are missing, so it falls short of the comprehensive-synonym anchor.	4 / 5
Distinctiveness Conflict Risk	'Microsoft Teams' is a clear niche with distinct triggers (messages/channels/meetings/chats) and minimal overlap risk with other skills; it would not fire for unrelated tasks.	5 / 5
	Total	17 / 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: davepoon/buildwithclaude
Path: plugins/all-skills/skills/microsoft-teams-automation/SKILL.md
Commit: a9fa86d

Reviewed: about 20 hours 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.