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.
36
3%
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 essentially a placeholder that repeats the skill name without explaining what it does or when it should be used. It lacks concrete actions, natural trigger terms, and explicit usage guidance, making it nearly useless for skill selection among multiple options.
Suggestions
Add concrete actions the skill performs, e.g., 'Sends messages, adaptive cards, and notifications to Microsoft Teams channels via incoming webhooks.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user wants to post a message to Teams, send a Teams notification, or configure a Teams incoming webhook.'
Remove the duplicated trigger term and replace with varied natural keywords users might say, such as 'Teams notification', 'post to Teams channel', 'Microsoft Teams webhook', 'send Teams message'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Teams Webhook Sender') without describing any concrete actions. There is no mention of what it actually does—e.g., sending messages, posting cards, formatting payloads—just a label and category. | 1 / 3 |
Completeness | Neither the 'what does this do' nor the 'when should Claude use it' questions are meaningfully answered. There is no 'Use when...' clause and no description of capabilities beyond the skill name. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('teams webhook sender, teams webhook sender'). There are no natural user keywords like 'send message to Teams', 'Teams notification', 'webhook', 'Microsoft Teams', or 'post to channel'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Teams Webhook' does point to a specific niche (Microsoft Teams webhooks), which provides some distinctiveness. However, the lack of concrete actions or triggers means it could still overlap with other messaging or notification skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no substantive content. It contains only meta-descriptions and trigger phrases but provides zero actionable guidance on how to actually send messages via Microsoft Teams webhooks. There are no code examples, no payload formats, no webhook URL instructions, and no workflow steps whatsoever.
Suggestions
Add a concrete, executable code example showing how to send a message to a Teams webhook (e.g., a Python requests.post call with the JSON payload format)
Include the actual Teams webhook payload schema with examples of cards, text messages, and adaptive cards
Define a clear workflow: 1) Create incoming webhook in Teams channel, 2) Construct payload, 3) Send POST request, 4) Validate response status code
Remove all meta-description sections (Purpose, When to Use, Example Triggers) and replace with actual instructional content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or concrete guidance. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no webhook URL format, no payload examples, no API details. The skill describes rather than instructs, offering only vague phrases like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. There is no sequence, no validation, and no concrete process for sending a Teams webhook message. The content is purely descriptive metadata. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed files, no structured sections with real content, and no navigation to deeper resources. | 1 / 3 |
Total | 4 / 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
4dee593
- 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.