CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

91

2.02x
Quality

88%

Does it follow best practices?

Impact

95%

2.02x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a clear, sequenced workflow and concrete examples, but it is longer than necessary due to repeated business-hours logic and does not properly split content across files — including a referenced examples.md that is missing from the bundle.

Suggestions

Create the referenced examples.md (or remove the dangling link) and move the detailed worked scenarios and special-case rules into it so the main body stays a lean overview.

De-duplicate the business-hours calculation logic that currently appears in both 'Examples' and 'Business Hours Calculation Rules' / 'Tips', keeping a single canonical worked example.

Trim or consolidate the 'Tips' section, which restates business-hours and edge-case rules already covered in 'Business Hours Calculation Rules' and 'Special Cases'.

DimensionReasoningScore

Conciseness

The ~277-line body is mostly efficient and avoids explaining concepts Claude already knows, but the same business-hours logic is repeated across 'Examples', 'Business Hours Calculation Rules', and 'Tips', so it could be tightened considerably.

2 / 3

Actionability

Provides a concrete SLA matrix, explicit formulas, multiple worked examples, a defined JSON output format, and a quality checklist — copy-paste-ready actionable guidance rather than vague direction.

3 / 3

Workflow Clarity

The 5-step calculation process is clearly sequenced and reinforced by a quality checklist with validation items; since this is a calculation rather than a destructive/batch operation, the missing-feedback-loop cap does not apply.

3 / 3

Progressive Disclosure

There is one signaled one-level reference ('See examples.md'), but that file does not actually exist in the bundle, and most detailed content (examples, escalation, special cases) is kept inline in an already-long body rather than split into separate files.

2 / 3

Total

10

/

12

Passed

Description

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.

The description is concise, concrete, and well-formed: it names the capability, its key inputs, and an explicit 'Use when' trigger clause with natural phrasing. It scores at the top across all dimensions with no fluff or over-claims.

DimensionReasoningScore

Specificity

States a concrete action ('Calculate SLA deadlines for support tickets') tied to specific inputs ('customer tier and urgency'), matching the anchor for listing concrete actions rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Calculate SLA deadlines for support tickets based on customer tier and urgency') and when ('Use when determining response deadlines...'), with an explicit 'Use when' clause.

3 / 3

Trigger Term Quality

Includes natural terms users would say — 'determining response deadlines', 'checking SLA compliance', 'SLA, deadline, or response time requirements' — giving good coverage rather than jargon.

3 / 3

Distinctiveness Conflict Risk

Targets a narrow niche (SLA deadlines for support tickets by tier/urgency) with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
udacity/cd14715-claude-code-classroom
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.