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 description is essentially a placeholder with no substantive content. It names a skill category and repeats the skill name as trigger terms but provides zero information about what the skill actually does, what types of notifications it handles, or when it should be selected. It would be nearly impossible for Claude to correctly choose this skill from a pool of available options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Routes notifications via email, SMS, Slack, and push channels based on user preferences and priority rules.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to send alerts, dispatch notifications, configure notification channels, or set up automated messaging workflows.'
Include distinct trigger keywords users would naturally say, such as 'send alert', 'notify', 'push notification', 'email alert', 'SMS', 'Slack message', 'webhook', to differentiate from other business automation skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. 'Notification Dispatcher' is a name, not a description of capabilities. There is no indication of what it actually does—no verbs describing 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 explicit 'Use when...' clause or equivalent trigger guidance. | 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', 'SMS', 'remind', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic. 'Business Automation' is a broad category, and 'Notification Dispatcher' without specifics could overlap with any skill involving notifications, messaging, alerts, or communication automation. | 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 a hollow placeholder that contains no actual instructional content. It describes what a notification dispatcher skill would theoretically do without providing any concrete guidance, code, examples, or workflows. It is entirely non-functional as a skill file.
Suggestions
Define what a 'notification dispatcher' actually is in this context and provide concrete, executable code examples (e.g., sending notifications via email, SMS, webhooks) with specific libraries and configurations.
Add a clear multi-step workflow for setting up and using the notification dispatcher, including validation steps (e.g., verify notification delivery, handle failures/retries).
Replace the meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') with actual actionable content—input/output examples, configuration templates, and specific commands.
If advanced topics exist (e.g., batching, rate limiting, multi-channel routing), reference them via clearly signaled links to separate files rather than listing vague capabilities.
| 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 token is wasted on describing the skill rather than teaching anything. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no specific steps, no examples of inputs/outputs. The 'capabilities' section lists vague promises like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. The skill content is purely a meta-description with no operational instructions. | 1 / 3 |
Progressive Disclosure | There is no meaningful content to organize, no references to detailed files, and no layered structure. The sections are superficial headings over empty platitudes with 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
c8a915c
- 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.