teams-notifications
Microsoft Teams MCP integration for agent-to-human notifications and bi-directional communication. Use when agents need to post progress updates, request approvals, or read user responses via Teams channels and chats.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies the platform (Microsoft Teams), the integration mechanism (MCP), and specific use cases (posting updates, requesting approvals, reading responses). It includes an explicit 'Use when' clause with natural trigger terms and is distinctive enough to avoid conflicts with other communication or notification skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'post progress updates', 'request approvals', 'read user responses'. Also specifies the communication pattern ('agent-to-human notifications and bi-directional communication') and the medium ('Teams channels and chats'). | 3 / 3 |
Completeness | Clearly answers both 'what' (Microsoft Teams MCP integration for notifications and bi-directional communication) and 'when' (explicit 'Use when agents need to post progress updates, request approvals, or read user responses via Teams channels and chats'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Microsoft Teams', 'Teams', 'notifications', 'approvals', 'channels', 'chats', 'progress updates', 'MCP'. These cover the main terms a user or agent would use when needing this capability. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets specifically Microsoft Teams as the platform, MCP as the integration type, and agent-to-human communication as the use case. Unlikely to conflict with other skills like Slack integrations or general notification skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently covers Teams MCP integration with concrete, executable examples and a well-structured approval workflow including validation, error handling, and escalation. The content is appropriately scoped with advanced topics deferred to a reference file. The only minor observation is that the Channel & Chat Conventions section is a bit thin, but this keeps the skill concise.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what Teams is, what MCP is, or how OAuth works—it assumes Claude knows these things. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | Provides concrete MCP tool call examples with JSON payloads, executable polling logic in JavaScript, specific regex patterns for approval detection, and clear fallback/retry behavior. The examples are copy-paste ready. | 3 / 3 |
Workflow Clarity | The Human-in-the-Loop Approval section is a clear 3-step workflow with explicit validation (verify message_id confirmation), error handling (retry once, fallback), polling parameters (5s interval, 5 min timeout), escalation on timeout, and an acknowledgment step. This is a well-structured feedback loop. | 3 / 3 |
Progressive Disclosure | The skill provides a concise overview with quick-start examples inline and appropriately defers advanced content (Adaptive Cards, rate limits, security) to a one-level-deep REFERENCE.md link that is clearly signaled with context about when to use it. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- monkilabs/opencastle
- Commit
18c6f2c
- 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.