configure-notifications
Configure notification integrations (Telegram, Discord, Slack) via natural language
42
43%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/configure-notifications/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear domain (notification integrations) and names specific platforms, which is helpful for differentiation. However, it lacks a 'Use when...' clause, provides only a single vague action ('configure'), and misses common trigger terms users might use. The phrase 'via natural language' describes the skill's interface rather than adding useful selection criteria.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to set up or manage notifications, webhooks, or alerts for Telegram, Discord, or Slack.'
Expand the action verbs to be more specific, e.g., 'Set up webhooks, configure notification channels, test message delivery, and manage alert routing for Telegram, Discord, and Slack integrations.'
Include additional natural trigger terms users might say, such as 'webhook', 'alerts', 'bot', 'notify', 'messaging', or 'chat notifications'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (notification integrations) and lists specific platforms (Telegram, Discord, Slack), but only describes one action ('configure') without detailing what configuration entails (e.g., setting up webhooks, managing channels, testing connections). | 2 / 3 |
Completeness | Describes what it does (configure notification integrations) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause should cap completeness at 2, and the 'what' portion is also thin, warranting a score of 1. | 1 / 3 |
Trigger Term Quality | Includes good platform-specific keywords (Telegram, Discord, Slack) and 'notification' which users might say, but misses common variations like 'webhook', 'alerts', 'bot setup', 'notifications', or 'messaging integration'. The phrase 'via natural language' describes how the skill works rather than serving as a trigger term. | 2 / 3 |
Distinctiveness Conflict Risk | The specific platform names (Telegram, Discord, Slack) help distinguish it, but 'notification integrations' is somewhat broad and could overlap with skills for general API configuration, chatbot setup, or platform-specific skills for those services. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is highly actionable with excellent workflow clarity — every step has concrete commands, validation, and error handling. However, it is severely bloated due to massive repetition across three nearly-identical provider flows plus custom integrations, all crammed into a single file. The content would benefit enormously from extracting shared patterns and splitting provider-specific guides into separate referenced files.
Suggestions
Extract the shared workflow steps (detect existing config, event selection, test notification, confirmation) into a common pattern section or separate file, then reference it from each provider section to eliminate ~60% of the repetition.
Split each provider (Telegram, Discord, Slack, Custom) into its own referenced file (e.g., TELEGRAM.md, DISCORD.md) with the main SKILL.md serving as a routing overview with links.
Remove explanatory text Claude already knows (e.g., what webhooks are, how Telegram bots work) and keep only the specific configuration values, formats, and commands needed.
Consolidate the template variables reference table — it appears in both the Hook Event Templates section and the Custom Integration section with slight variations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This skill is extremely verbose at ~600+ lines. There is massive repetition across the three providers (Telegram, Discord, Slack) — the detect-existing-config, event selection, test notification, and confirmation steps are nearly identical each time. The content could be dramatically reduced by abstracting shared patterns. Additionally, it explains things Claude already knows (what Telegram/Discord/Slack are, how webhooks work). | 1 / 3 |
Actionability | The skill provides fully executable bash/curl commands, concrete jq operations for config manipulation, specific validation patterns (URL formats, token formats), exact AskUserQuestion prompts with options, and complete JSON config schemas. Every step has copy-paste ready code or precise instructions. | 3 / 3 |
Workflow Clarity | Each provider follows a clear numbered sequence with explicit validation checkpoints (token format validation, URL validation, test notification with error diagnosis). There are feedback loops for invalid input (re-ask), test-then-verify steps, and clear error recovery guidance with common failure modes listed. | 3 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no bundle files to offload content to. The three provider setups (Telegram, Discord, Slack), hook event templates, and custom integrations are all inlined in a single massive file. The shared patterns (event selection, testing, confirmation) should be extracted to separate files, and each provider could be its own referenced document. | 1 / 3 |
Total | 8 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (1215 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- Yeachan-Heo/oh-my-claudecode
- Commit
3e94567
- 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.