sla-calculation
Calculate SLA deadlines for support tickets based on customer tier and urgency. Use when determining response deadlines, checking SLA compliance, or when user asks about SLA, deadline, or response time requirements.
75
63%
Does it follow best practices?
Impact
95%
2.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./lesson-04-claude-code-config/exercise/solution/.claude/skills/sla-calculation/SKILL.mdQuality
Discovery
100%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 is a well-crafted skill description that clearly communicates its purpose, includes an explicit 'Use when' clause with natural trigger terms, and occupies a distinct niche. It uses proper third-person voice and is concise without being vague. It closely matches the good examples provided in the rubric.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Calculate SLA deadlines', 'based on customer tier and urgency', 'determining response deadlines', 'checking SLA compliance'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (calculate SLA deadlines for support tickets based on customer tier and urgency) and 'when' (explicit 'Use when' clause covering response deadlines, SLA compliance, and trigger terms like SLA, deadline, response time requirements). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'SLA', 'deadline', 'response time', 'support tickets', 'customer tier', 'urgency', 'SLA compliance'. Good coverage of terms a user would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche combining SLA calculations, support tickets, customer tiers, and urgency levels. Unlikely to conflict with other skills due to the very targeted domain of SLA deadline computation. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive SLA calculation guidance with a clear matrix and good worked examples, but suffers significantly from verbosity—it's roughly 3-4x longer than needed. Many sections repeat information (Tips restates business hours rules, Success Criteria states obvious goals), and the content lacks executable code despite being a calculation-focused skill. The broken reference to examples.md and monolithic structure further weaken it.
Suggestions
Cut content by 60%+: Remove 'When to Use This Skill' (covered by frontmatter), 'Tips' (repeats earlier rules), 'Success Criteria' (obvious), and 'Integration with Classification' (workflow context). Merge 'Special Cases' into the relevant sections.
Either provide executable Python/JS code for the business hours calculation or consolidate the pseudocode into a single clear algorithm block rather than spreading arithmetic across multiple sections.
Either create the referenced examples.md bundle file with the detailed worked examples, or remove the broken reference and keep only 1-2 inline examples.
Add a validation step in the workflow: after calculating the deadline, verify it falls on a business day/hour (for business hours SLAs) and sanity-check that the time remaining is non-negative.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~200+ lines. Includes unnecessary sections like 'When to Use This Skill' (duplicates frontmatter triggers), 'Tips' that repeat earlier content, 'Success Criteria' that states obvious quality goals, and 'Integration with Classification' that describes workflow context Claude doesn't need. The 'Special Cases' section on timezone handling and multiple SLA tiers is padded with obvious guidance. Much of this could be condensed to the SLA matrix, business hours rules, and output format. | 1 / 3 |
Actionability | The SLA matrix and business hours calculation rules are concrete and specific, and the output JSON schema is well-defined. However, there's no executable code—the 'code' blocks are pseudocode/arithmetic notation rather than runnable implementations. The calculation process describes steps conceptually rather than providing a concrete algorithm Claude could execute directly. | 2 / 3 |
Workflow Clarity | The 5-step calculation process is clearly sequenced and the examples walk through calculations step-by-step. However, there are no validation checkpoints—no step to verify the calculation is correct, no feedback loop for edge cases that might produce unexpected results. The quality checklist at the end is a post-hoc review rather than an integrated validation step within the workflow. | 2 / 3 |
Progressive Disclosure | References examples.md but no bundle file exists, making this a broken reference. The content is a monolithic wall of text with everything inline—the SLA matrix, all examples, business hours rules, special cases, tips, and success criteria are all in one file when much of this (especially the detailed examples and edge cases) could be split out. The structure is flat rather than layered. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- udacity/cd14715-claude-code-classroom
- Commit
6820a25
- 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.