notification-dispatcher
Notification Dispatcher - Auto-activating skill for Business Automation. Triggers on: notification dispatcher, notification dispatcher Part of the Business Automation skill category.
31
Quality
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 fails to describe any capabilities, actions, or use cases, and the trigger terms are just the skill name duplicated. Claude would have no meaningful information to determine when to select this skill over others.
Suggestions
Add specific actions the skill performs (e.g., 'Sends email notifications, SMS alerts, push notifications, and webhook callbacks based on business events or triggers').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user needs to send alerts, notify team members, dispatch messages, or set up automated notifications').
Remove the redundant duplicate trigger term and replace with varied, natural keywords like 'send notification', 'alert', 'notify', 'dispatch message', 'automated alerts'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Notification Dispatcher') and its category ('Business Automation') without describing any concrete actions. There are no verbs indicating what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no use cases or explicit trigger guidance beyond the redundant skill name). | 1 / 3 |
Trigger Term Quality | The triggers listed are just the skill name repeated twice ('notification dispatcher, notification dispatcher'). No natural user keywords like 'send alerts', 'notify users', 'push notifications', or 'email alerts' are included. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Business Automation' is extremely generic and could overlap with many other skills. 'Notification Dispatcher' provides some specificity but without describing what notifications or dispatching means, it remains unclear. | 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 content is essentially a placeholder template with no substantive guidance. It describes what a notification dispatcher skill would do in abstract terms but provides zero actionable information about how to actually implement notification dispatching - no code, no APIs, no message formats, no integration patterns.
Suggestions
Add concrete, executable code examples showing how to dispatch notifications (e.g., email via SMTP, SMS via Twilio, push notifications via Firebase)
Define a clear workflow with steps: compose message → validate recipient → send → verify delivery → handle failures
Include specific message format templates and configuration examples for common notification channels
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with actual implementation guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actionable information. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that waste tokens without teaching Claude anything specific. | 1 / 3 |
Actionability | No concrete code, commands, or specific instructions are provided. The skill describes what it supposedly does but never shows how to actually dispatch notifications - no API calls, no message formats, no integration examples. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The content only describes trigger phrases and vague capabilities without any actual process for notification dispatching. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative document with no references to detailed materials, no links to implementation guides, and no structured navigation to deeper content. It mentions 'Related Skills' but provides no actual links. | 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
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.