configure-notifications
Configure notification integrations (Telegram, Discord, Slack) via natural language
56
47%
Does it follow best practices?
Impact
Pending
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 and specific platforms but lacks explicit trigger guidance ('Use when...'), which significantly limits Claude's ability to know when to select this skill. The single action verb 'configure' and absence of natural user trigger terms weaken its effectiveness for skill selection among many options.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to set up notifications, configure alerts, or connect Telegram/Discord/Slack bots'
Expand the action verbs beyond 'configure' to include related capabilities like 'set up webhooks, manage notification channels, test integrations'
Include additional natural trigger terms users might say: 'alerts', 'notifications', 'bot', 'webhook', 'messaging'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (notification integrations) and lists specific platforms (Telegram, Discord, Slack), but 'configure' is a single action and 'via natural language' describes the method rather than additional concrete capabilities. | 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. | 1 / 3 |
Trigger Term Quality | Includes good platform-specific keywords (Telegram, Discord, Slack) that users would naturally mention, but misses common variations like 'notifications', 'alerts', 'webhooks', 'bot setup', or 'messaging integrations'. | 2 / 3 |
Distinctiveness Conflict Risk | The specific platform names (Telegram, Discord, Slack) provide some distinctiveness, but 'notification integrations' could overlap with other integration or messaging skills without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is highly actionable with excellent workflow clarity, providing complete executable code and clear step-by-step processes with validation checkpoints. However, it suffers from severe verbosity—the three provider sections (Telegram, Discord, Slack) repeat nearly identical structures that could be abstracted into a shared pattern. The monolithic structure also hurts progressive disclosure.
Suggestions
Extract common wizard steps (detect config, configure events, test, confirm) into a shared pattern section, then reference it from each provider with only provider-specific differences inline
Move Hook Event Templates and Custom Integration sections to separate referenced files (e.g., HOOK-TEMPLATES.md, CUSTOM-INTEGRATIONS.md)
Consolidate the three provider sections by creating a template structure and noting only the differences (URL format, API endpoints, mention syntax) per provider
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~700+ lines. Contains significant redundancy across the three provider sections (Telegram, Discord, Slack) with nearly identical step structures repeated. Much content could be consolidated into shared patterns with provider-specific differences noted. | 1 / 3 |
Actionability | Provides fully executable bash scripts, curl commands, and jq operations throughout. Code examples are copy-paste ready with clear variable placeholders. Validation patterns and test commands are concrete and complete. | 3 / 3 |
Workflow Clarity | Each provider section follows a clear numbered sequence with explicit validation steps (Step 8: Test the Configuration), error handling guidance (common issues listed), and feedback loops (if invalid, explain and ask again). The detect-existing-config pattern ensures safe reconfiguration. | 3 / 3 |
Progressive Disclosure | Uses routing section to direct to appropriate provider, but all content is inline in one massive file. The Hook Event Templates and Custom Integration sections could be separate files. References to related files exist but the main content is monolithic. | 2 / 3 |
Total | 9 / 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
48ffaac
- 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.