notification-dispatcher
Notification Dispatcher - Auto-activating skill for Business Automation. Triggers on: notification dispatcher, notification dispatcher Part of the Business Automation skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill notification-dispatcherOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is essentially a placeholder that provides no meaningful information about the skill's capabilities. It only states the skill name, repeats it as a trigger, and mentions a broad category. Claude would have no basis for selecting this skill appropriately from a list of available skills.
Suggestions
Add specific actions the skill performs (e.g., 'Sends email notifications, SMS alerts, push notifications, and Slack messages based on triggered events')
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user wants to send alerts, notify team members, dispatch messages, or set up automated notifications')
Specify the types of notifications supported and integration points to distinguish from other automation skills
| 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 triggers beyond the skill name). Both components are missing. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'notification dispatcher' repeated twice, which is the skill's own name rather than natural keywords users would say. Missing terms like 'send notification', 'alert', 'message', 'notify users', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic - 'Business Automation' could apply to dozens of skills. Without specific capabilities or use cases, it provides no clear niche to distinguish it from other automation-related skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is an empty template that provides no actual instruction on notification dispatching. It consists entirely of generic meta-descriptions about what the skill claims to do without any concrete implementation details, code examples, or actionable guidance. The content fails to teach Claude anything about how to actually dispatch notifications.
Suggestions
Add concrete code examples showing how to dispatch notifications (e.g., email, SMS, webhook implementations with specific libraries)
Define a clear workflow with steps like: 1) Determine notification type, 2) Format message, 3) Select channel, 4) Send with retry logic, 5) Validate delivery
Remove all meta-descriptions ('This skill provides...', 'Capabilities include...') and replace with actual executable guidance
Include specific examples of notification payloads, API calls, or configuration patterns that Claude can directly use
| 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 claims to do ('generates production-ready code') but never actually shows how to dispatch notifications or provides any executable guidance. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. The skill mentions 'step-by-step guidance' but provides none. There are no sequences, validation checkpoints, or any actual process to follow. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no examples, and no navigation to supporting documentation. It's essentially a placeholder with no real content to disclose. | 1 / 3 |
Total | 4 / 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.