sla-monitor-setup
Sla Monitor Setup - Auto-activating skill for Enterprise Workflows. Triggers on: sla monitor setup, sla monitor setup Part of the Enterprise Workflows skill category.
35
3%
Does it follow best practices?
Impact
95%
0.98xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/20-enterprise-workflows/sla-monitor-setup/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 essentially a placeholder that restates the skill name without providing any meaningful information about what the skill does or when it should be used. It lacks concrete actions, natural trigger terms, and explicit usage guidance, making it nearly useless for skill selection among a large set of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures SLA monitoring rules, sets threshold alerts, tracks service level compliance, and generates SLA breach reports.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about setting up SLA monitoring, service level agreements, uptime tracking, SLA alerts, compliance thresholds, or breach notifications.'
Expand trigger terms to include natural variations users would say: 'SLA', 'service level agreement', 'uptime monitoring', 'SLA alerts', 'SLA compliance', 'monitoring setup'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Sla Monitor Setup') without describing any concrete actions. There are no specific capabilities listed—no verbs like 'configure', 'track', 'alert', or 'define thresholds'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond restating the skill name, and there is no explicit 'when to use' guidance. The 'Triggers on' line is just a duplicate of the skill name, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'sla monitor setup' repeated twice. There are no natural variations a user might say, such as 'SLA tracking', 'service level agreement', 'monitoring thresholds', 'SLA alerts', or 'uptime monitoring'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'SLA monitor setup' is somewhat specific to a niche domain, which reduces conflict risk slightly. However, without concrete actions or clear scope, it could overlap with other enterprise monitoring or SLA-related 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—a template placeholder with no actual content about SLA monitor setup. It contains only meta-descriptions of what the skill claims to do without any actionable instructions, code, configurations, or concrete guidance. It provides zero value to Claude in performing SLA monitoring tasks.
Suggestions
Add concrete, executable content: include specific code/configuration examples for setting up SLA monitors (e.g., defining SLA thresholds, configuring alerting rules, setting up monitoring dashboards).
Define a clear multi-step workflow with validation checkpoints, such as: 1) Define SLA metrics, 2) Configure monitoring tool, 3) Set alert thresholds, 4) Validate alerts fire correctly, 5) Set up escalation paths.
Remove all meta-description sections ('Purpose', 'When to Use', 'Capabilities', 'Example Triggers') that describe the skill rather than teaching how to perform the task—these belong in YAML frontmatter, not the body.
Add specific tool/platform guidance (e.g., Prometheus, Datadog, PagerDuty) with copy-paste-ready configuration snippets for common SLA monitoring patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual guidance, wasting tokens on meta-descriptions like 'Provides step-by-step guidance' without ever providing that guidance. | 1 / 3 |
Actionability | There is zero concrete, executable guidance—no code, no commands, no specific steps, no configurations. Every section describes what the skill could do rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' there are no steps, no sequence, and no validation checkpoints for SLA monitor setup. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions with no references to detailed materials, no links to related files, and no structured navigation to deeper content. | 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
4dee593
- 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.