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

65%

Does it follow best practices?

Impact

95%

1.46x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.trae/skills/microsoft-teams-automation/SKILL.md

Quality

Discovery

67%

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 does a good job listing specific capabilities for Microsoft Teams automation and is clearly distinguishable from other skills due to its platform and integration specificity. However, it lacks an explicit 'Use when...' clause, and the trigger terms could be expanded to include more natural user language variations beyond the core action verbs.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Microsoft Teams, sending Teams messages, scheduling Teams meetings, or managing Teams channels.'

Include more natural trigger term variations users might say, such as 'Teams call', 'schedule a meeting in Teams', 'DM on Teams', or 'Teams notification'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'send messages, manage channels, create meetings, handle chats, and search messages.' These are clear, actionable capabilities.	3 / 3
Completeness	Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause. The 'when' is only implied by the nature of the actions listed, which caps this at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Includes relevant keywords like 'Microsoft Teams', 'messages', 'channels', 'meetings', 'chats', but misses common user variations like 'Teams call', 'schedule a meeting', 'DM', 'team chat', or file-related terms. The mention of 'Rube MCP (Composio)' is technical jargon unlikely to be used by end users.	2 / 3
Distinctiveness Conflict Risk	Clearly scoped to Microsoft Teams via a specific integration (Rube MCP/Composio). The combination of platform (Teams) and integration method makes it highly distinctive and unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Implementation

62%

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

This is a comprehensive Microsoft Teams automation skill with well-structured workflows and clear tool sequencing. Its main weaknesses are verbosity (repeated pitfall information across sections), lack of concrete executable examples with actual parameter values, and a monolithic structure that could benefit from splitting detailed reference material into separate files. The workflow clarity is strong with good prerequisite labeling and error handling guidance.

Suggestions

Add concrete tool call examples with actual parameter values (e.g., a complete RUBE_SEARCH_TOOLS call followed by a TEAMS_POST_CHANNEL_MESSAGE call with realistic parameters) to improve actionability.

Consolidate repeated pitfall information (ID formats, pagination, rate limits) into the 'Known Pitfalls' section only, and remove duplicates from individual workflow sections to reduce token usage.

Move the quick reference table and detailed Known Pitfalls into a separate REFERENCE.md file, keeping SKILL.md focused on the core workflows and setup.

Dimension	Reasoning	Score
Conciseness	The skill is fairly well-organized but is quite lengthy (~200+ lines). Some sections are repetitive (e.g., pitfalls about IDs and pagination are repeated across workflows and again in 'Known Pitfalls'). The quick reference table adds value but the overall content could be tightened significantly.	2 / 3
Actionability	Tool sequences are clearly named and parameters are specified, which is good. However, there's no executable code—just pseudocode-style numbered steps and plain text patterns. The instruction to 'always call RUBE_SEARCH_TOOLS first' is actionable, but actual tool call examples with concrete parameter values are missing.	2 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with labeled steps (Prerequisite/Optional/Required), explicit tool ordering, and pitfall callouts at each stage. Validation is addressed through connection status checks and error handling guidance (403, 429, pagination). The setup flow includes a clear checkpoint ('Confirm connection status shows ACTIVE before running any workflows').	3 / 3
Progressive Disclosure	Content is well-structured with clear headers and a quick reference table, but everything is in a single monolithic file. The extensive pitfalls, pagination patterns, and detailed parameter lists for 14+ tools could be split into referenced sub-files. The single external link to Composio docs is helpful but insufficient for the volume of content present.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: Lingjie-chen/MT5
Commit: 3069d33

Reviewed: 26 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.