creating-alerting-rules
Execute this skill enables AI assistant to create intelligent alerting rules for proactive performance monitoring. it is triggered when the user requests to "create alerts", "define monitoring rules", or "set up alerting". the skill helps define thresholds, rou... Use when generating or creating new content. Trigger with phrases like 'generate', 'create', or 'scaffold'.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill creating-alerting-rules38
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
42%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 suffers from internal contradiction - it starts describing a specific monitoring/alerting skill but ends with an extremely generic 'Use when' clause about creating any content. The description appears truncated, and the generic trigger terms ('generate', 'create') would cause this skill to incorrectly activate for unrelated tasks.
Suggestions
Remove or replace the generic 'Use when generating or creating new content' clause with monitoring-specific triggers like 'Use when the user wants to set up alerts, define monitoring thresholds, or configure performance notifications'
Add more specific trigger terms users would naturally say: 'alert thresholds', 'monitoring alerts', 'performance alerts', 'notification rules', 'SLA monitoring'
Complete the truncated description and ensure the 'what' (monitoring alerts) aligns with the 'when' (monitoring-related user requests)
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (alerting rules, performance monitoring) and some actions (create alerts, define thresholds), but the description is truncated and uses vague language like 'intelligent alerting rules' without listing comprehensive concrete actions. | 2 / 3 |
Completeness | Has a 'Use when' clause but it's generic ('generating or creating new content') and contradicts the specific monitoring focus. The description is truncated ('rou...') suggesting incomplete content, and the what/when don't align coherently. | 2 / 3 |
Trigger Term Quality | Includes some relevant triggers ('create alerts', 'define monitoring rules', 'set up alerting', 'generate', 'create', 'scaffold') but mixes overly generic terms ('generate', 'create') that would conflict with many other skills, and the monitoring-specific terms are limited. | 2 / 3 |
Distinctiveness Conflict Risk | The generic triggers 'generate', 'create', 'scaffold' would conflict with virtually any content-creation skill. The 'Use when generating or creating new content' clause is extremely broad and undermines the monitoring-specific focus. | 1 / 3 |
Total | 7 / 12 Passed |
Implementation
12%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a generic template with minimal actionable content. It describes what alerting rules are and what the skill conceptually does, but provides no concrete alert syntax, threshold configurations, routing rule examples, or executable code. The content is padded with boilerplate sections that add no value and fails to respect Claude's existing knowledge.
Suggestions
Replace abstract descriptions with concrete, executable alert rule examples in the actual syntax/format used by the monitoring system (e.g., Prometheus alerting rules, Datadog monitors, PagerDuty configurations)
Add specific threshold values and formulas with real examples, such as 'latency_p99 > 500ms for 5m' rather than 'prompt for latency thresholds'
Include a sample runbook template with actual diagnostic commands and resolution steps that can be copied and customized
Remove generic boilerplate sections (Prerequisites, Instructions, Output, Error Handling) and replace with specific tool integrations and validation commands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive padding and explanations of concepts Claude already knows. Sections like 'Prerequisites', 'Instructions', 'Output', and 'Error Handling' are generic boilerplate that add no value. The content explains what alerting is rather than providing actionable guidance. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples. The 'Examples' section describes what the skill 'will do' abstractly rather than showing actual alert configurations, threshold syntax, or routing rule formats. Everything is vague description rather than copy-paste ready guidance. | 1 / 3 |
Workflow Clarity | The 'How It Works' section lists steps in sequence, but lacks any validation checkpoints, specific commands, or feedback loops. No guidance on how to verify alerts are working correctly or how to test configurations before deployment. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files for detailed content. The 'Resources' section mentions 'Project documentation' and 'Related skills' without any actual links or file references. Content that could be split (runbook templates, threshold examples) is either missing or vaguely described inline. | 1 / 3 |
Total | 5 / 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 — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 |
Total | 13 / 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.