teams-webhook-sender
Teams Webhook Sender - Auto-activating skill for Business Automation. Triggers on: teams webhook sender, teams webhook sender Part of the Business Automation skill category.
39
Quality
7%
Does it follow best practices?
Impact
99%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/teams-webhook-sender/SKILL.mdQuality
Discovery
7%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 description is severely underdeveloped, essentially just restating the skill name without explaining capabilities or providing meaningful trigger guidance. It lacks any concrete actions, natural user keywords, or explicit 'Use when' clauses. The only slight positive is that 'Teams Webhook' at least identifies a specific platform.
Suggestions
Add specific actions the skill performs, e.g., 'Sends formatted messages, alerts, and notifications to Microsoft Teams channels via incoming webhooks'
Include a 'Use when...' clause with natural trigger terms like 'send to Teams', 'Teams notification', 'post message to Teams channel', 'Microsoft Teams alert', 'webhook message'
Remove the duplicate trigger term and expand with variations users would naturally say when needing this functionality
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Teams Webhook Sender') without describing any concrete actions. There are no verbs or specific capabilities listed - it doesn't explain what sending to Teams webhooks actually involves or what operations are supported. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just a duplicate of the skill name. There is no 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('teams webhook sender, teams webhook sender'). Missing natural variations users would say like 'send message to Teams', 'Teams notification', 'post to Teams channel', 'Microsoft Teams', or 'webhook'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Teams Webhook' is somewhat specific to Microsoft Teams integrations, which provides some distinctiveness. However, the vague 'Business Automation' category and lack of specific use cases could cause overlap with other notification or messaging skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a generic template with no actual Teams webhook implementation content. It describes capabilities abstractly without providing any concrete code, webhook URL formats, payload structures, or HTTP request examples. The content would be useless for Claude trying to help a user send a Teams webhook message.
Suggestions
Add executable Python/curl code showing how to POST to a Teams webhook URL with proper payload structure
Include the Teams Adaptive Card JSON schema or MessageCard format with a concrete example
Provide the webhook URL format and explain how users obtain their webhook URL from Teams
Add error handling guidance for common failures (401, 400, rate limits) with specific response codes
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Teams webhooks. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that waste tokens without adding value. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly ('Generates production-ready code') but never actually shows how to send a Teams webhook message or provides any executable examples. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The content lists vague capabilities but provides no sequence for actually implementing a Teams webhook sender, no validation steps, and no error handling guidance. | 1 / 3 |
Progressive Disclosure | The content has some structure with clear section headers, but there are no references to detailed documentation, no links to examples, and the sections themselves contain no substantive content to organize. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
0c08951
- 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.