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 disambiguation. However, it lacks a 'Use when...' clause, provides only a single vague action ('configure'), and misses common trigger terms users might employ. The phrase 'via natural language' is more of a method description than a capability and adds little value for skill selection.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to set up or manage notifications, webhooks, or bot integrations for Telegram, Discord, or Slack.'
Expand the specific actions beyond 'configure', e.g., 'Set up webhooks, manage notification channels, test message delivery, and troubleshoot notification integrations for Telegram, Discord, and Slack.'
Include additional natural trigger terms like 'webhook', 'alerts', 'bot', 'messaging', 'chat notifications' to improve keyword coverage.
| 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, missing 'Use when' caps completeness at 2, and the 'what' is also thin, warranting a 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', 'messaging', or 'chat integration' that users would naturally use. | 2 / 3 |
Distinctiveness Conflict Risk | The specific platform names (Telegram, Discord, Slack) and 'notification integrations' provide some distinctiveness, but 'configure' is generic and could overlap with general configuration or platform-specific skills. The 'via natural language' phrase is vague and doesn't help differentiate. | 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 executable code, validation, error handling, and testing. However, it is severely bloated due to massive repetition across three nearly-identical provider flows and the custom integration section, all crammed into a single file. The content would benefit enormously from extracting shared patterns and splitting provider-specific details into separate files.
Suggestions
Extract the shared workflow pattern (detect config → collect credentials → configure events → write config → test → confirm) into a common section, then have each provider section only specify its unique fields (token format, API endpoints, validation rules).
Split each provider (Telegram, Discord, Slack, Custom) into separate referenced files (e.g., TELEGRAM.md, DISCORD.md) and keep SKILL.md as a routing overview with the provider selection logic.
Remove explanatory text Claude already knows (e.g., what webhooks are, how curl works, what Telegram bots are) — just provide the specific formats, URLs, and validation patterns needed.
Consolidate the repeated event-selection and config-writing code blocks into a single reusable section referenced by all providers.
| 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, configure-events, write-configuration, and test steps are nearly identical each time. The content could be dramatically reduced by abstracting shared patterns. Additionally, it explains concepts Claude already knows (what Telegram bots are, what webhooks are, how curl works). | 1 / 3 |
Actionability | The skill provides fully executable bash commands, concrete jq operations, specific curl commands for testing, validation patterns, and exact JSON config schemas. Every step has copy-paste ready code with real examples of tokens, URLs, and config structures. | 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 failures (common issues listed with solutions), and existing config detection before modification. | 3 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no bundle files to offload content to. The three provider sections (Telegram, Discord, Slack) plus custom integrations and hook templates are all inlined in a single massive file. The shared patterns (event selection, config writing, testing) should be extracted to separate files, with each provider section being much shorter. References to source files at the bottom are minimal and don't help with navigation. | 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
679b418
- 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.