notification-dispatcher
Notification Dispatcher - Auto-activating skill for Business Automation. Triggers on: notification dispatcher, notification dispatcher Part of the Business Automation skill category.
31
0%
Does it follow best practices?
Impact
85%
0.96xAverage 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/notification-dispatcher/SKILL.mdQuality
Discovery
0%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 an extremely weak skill description that reads like an auto-generated template with no meaningful content. It fails on every dimension: no concrete actions, no natural trigger terms, no explanation of when to use it, and nothing to distinguish it from other skills. The trigger terms are just the skill name duplicated.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Routes notifications to appropriate channels (email, SMS, Slack, push), formats notification content, manages notification schedules and batching.'
Add a 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to send notifications, dispatch alerts, route messages to channels, or set up automated notification workflows.'
Include distinct keywords users would naturally say, such as 'send alert', 'notify', 'email notification', 'push notification', 'message dispatch', 'notification routing'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. 'Notification Dispatcher' is a label, not a description of capabilities. There is no indication of what it actually does—no verbs describing specific actions like sending, routing, formatting, or scheduling notifications. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no meaningful 'Use when...' clause. The 'Triggers on' line is just the skill name repeated. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'notification dispatcher' repeated twice. These are not natural keywords a user would say. Users would more likely say things like 'send notification', 'alert', 'email', 'push notification', 'notify users', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic. 'Business Automation' is a broad category, and without specific actions or triggers, this could conflict with any automation-related skill. Nothing distinguishes it from other notification or messaging skills. | 1 / 3 |
Total | 4 / 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 placeholder that contains no actual instructional content. It describes itself in abstract, marketing-like language without providing any concrete guidance, code, commands, or workflows for notification dispatching. It fails on every dimension because it teaches Claude nothing it could act on.
Suggestions
Add concrete, executable code examples showing how to dispatch notifications (e.g., sending emails via SMTP, posting to Slack webhooks, or using a message queue).
Define a clear multi-step workflow with validation checkpoints, such as: 1) Configure notification channels, 2) Build message payload, 3) Validate payload schema, 4) Send notification, 5) Verify delivery status.
Remove all meta-description sections ('Purpose', 'When to Use', 'Capabilities', 'Example Triggers') that describe the skill rather than instruct, and replace them with actionable content.
If the skill covers multiple notification channels or patterns, split detailed guides into referenced files (e.g., EMAIL.md, SLACK.md) and keep SKILL.md as a concise overview with clear links.
| 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 specific steps, no examples of actual notification dispatching. The 'Example Triggers' section just lists phrases to activate the skill, not how to accomplish anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to supporting files, no structured navigation, and no separation of overview from detail—because there is no detail to separate. | 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
3a2d27d
- 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.