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.
Overall
score
23%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill teams-webhook-senderActivation
7%This description is severely underdeveloped, consisting primarily of the skill name and category metadata without any substantive explanation of capabilities or usage triggers. It fails to describe what actions the skill performs and provides no natural language triggers that users would actually say when needing this functionality.
Suggestions
Add specific actions the skill performs, e.g., 'Sends messages, notifications, and alerts to Microsoft Teams channels via incoming webhooks'
Include a 'Use when...' clause with natural trigger terms like 'post to Teams', 'Teams notification', 'send Teams message', 'Microsoft Teams alert', 'channel notification'
Describe the types of content that can be sent (text messages, formatted cards, alerts) to help Claude understand the full capability scope
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Teams Webhook Sender') without describing any concrete actions. There's no explanation of what it actually does - no verbs like 'sends', 'posts', 'notifies', or specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just the skill name repeated. There's no 'Use when...' clause or explicit 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 user phrases like 'send message to Teams', 'post to Teams channel', 'Teams notification', or 'Microsoft Teams'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Teams Webhook' provides some specificity that distinguishes it from generic messaging skills, but 'Business Automation' is vague and could overlap with many other automation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%This skill is a placeholder template with no actual instructional content. It describes what a Teams webhook sender skill would do but provides zero actionable guidance—no webhook URL format, no payload structure, no code examples, and no workflow steps. Claude already knows what Teams webhooks are; this skill adds nothing useful.
Suggestions
Add executable code showing how to send a Teams webhook message with a complete Python/curl example including the webhook URL format and JSON payload structure
Include the required JSON schema for Teams Adaptive Cards or simple message formats with concrete examples
Add a workflow with validation steps: construct payload -> send request -> check response status -> handle errors
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with specific Teams webhook constraints and gotchas
| 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 instructions are provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance, webhook URLs, payload formats, or executable examples. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for sending a Teams webhook message, no validation of webhook responses, and no error handling guidance. The content only describes triggers for activation, not how to perform the task. | 1 / 3 |
Progressive Disclosure | The content has some structure with clear section headers, but there's no actual content to disclose progressively. No references to detailed documentation, API specs, or examples are provided. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.