alertmanager-rules-config
Alertmanager Rules Config - Auto-activating skill for DevOps Advanced. Triggers on: alertmanager rules config, alertmanager rules config Part of the DevOps Advanced skill category.
36
3%
Does it follow best practices?
Impact
96%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/02-devops-advanced/alertmanager-rules-config/SKILL.mdQuality
Discovery
7%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 is extremely weak across all dimensions. It reads as auto-generated boilerplate with no concrete actions, no natural trigger terms, and no explicit guidance on when to use the skill. The only slight positive is that 'Alertmanager' is a somewhat distinctive domain term, but the description fails to leverage this with any meaningful detail.
Suggestions
Add specific concrete actions such as 'Creates, validates, and edits Alertmanager routing rules, receiver configurations, and inhibition rules in YAML format'.
Add a 'Use when...' clause with natural trigger terms like 'alertmanager config', 'alert routing', 'Prometheus alerts', 'notification receivers', 'alerting rules YAML', 'silence rules'.
Remove the duplicated trigger term and the generic 'Auto-activating skill for DevOps Advanced' filler text, replacing it with actionable capability descriptions.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. It only names 'Alertmanager Rules Config' without describing what it actually does — no verbs like 'create', 'validate', 'edit', or 'manage' are present. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause — only a vague auto-activation mention. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'alertmanager rules config' repeated twice. There are no natural variations a user might say, such as 'alert rules', 'Prometheus alerting', 'alertmanager configuration', 'alerting setup', or '.yml alert config'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Alertmanager Rules Config' is somewhat specific to a niche domain (Prometheus/Alertmanager), which provides some distinctiveness, but the lack of concrete actions or clear triggers means it could overlap with general DevOps or monitoring configuration skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no actual content. It consists entirely of meta-descriptions about what the skill supposedly does without providing any actual alertmanager rules configuration guidance, examples, YAML snippets, or actionable instructions. It would provide zero value to Claude when attempting to help with alertmanager configuration tasks.
Suggestions
Add concrete Alertmanager rule configuration examples in YAML format, including alerting rules (e.g., high CPU, disk space) with proper group_by, match, and receiver configurations.
Include a workflow for creating and validating alertmanager rules: write rule → validate with `amtool check-config` → test with `amtool config routes test` → deploy.
Provide specific best practices such as proper inhibition rules, routing trees, grouping strategies, and common pitfalls (e.g., over-alerting, missing severity labels).
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual technical content like rule syntax reference and production-ready configuration templates.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It repeats 'alertmanager rules config' numerous times without providing any actual configuration guidance, rules syntax, or examples. Every line is padding that tells Claude nothing it doesn't already know. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no configuration examples, no commands, no YAML snippets for alertmanager rules. Phrases like 'Provides step-by-step guidance' and 'Generates production-ready code' are meta-descriptions, not actual instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content has section headers but they contain no useful information. There are no references to detailed files, no links to examples or advanced topics, and no meaningful content organization beyond boilerplate headings. | 1 / 3 |
Total | 4 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3e83543
- 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.