CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

87

2.02x
Quality

85%

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%Weight 40%Scale 1-5

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

The content is highly actionable with a clear, well-sequenced workflow and concrete examples, but it is somewhat repetitive and leans on a dangling reference (examples.md) while inlining material that would benefit from separation.

Suggestions

Either create examples.md with the worked scenarios or remove the dangling 'See examples.md' reference to avoid a broken navigation link.

Consolidate the business-hours calculation rules into a single section; the same weekend/holiday/EOD logic is repeated in Step 3, 'Business Hours Calculation Rules', and 'Tips', which inflates the token budget.

Move the detailed SLA matrix and/or worked examples into a separate reference file to reduce inline bulk and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is largely actionable but noticeably repetitive — business-hours calculation rules are restated in the Calculation Process, again in 'Business Hours Calculation Rules', and again in 'Tips' — so it is 'mostly efficient but could be tightened' rather than lean (4-5) yet not severely padded (1-2).

3 / 5

Actionability

Provides a concrete SLA matrix, executable formulas, three fully worked examples, and a copy-paste-ready JSON output schema covering common cases, matching the 'fully executable' anchor; it is not a 4 because examples are complete rather than having minor gaps.

5 / 5

Workflow Clarity

A clearly sequenced 5-step process with explicit risk thresholds, escalation triggers, and a quality checklist acting as validation checkpoints; this is a non-destructive calculation skill so the batch/destructive cap does not apply, and the checkpoints match the top anchor.

5 / 5

Progressive Disclosure

Sections are reasonably organized, but the only external reference ('See examples.md') points to a file that does not exist in the bundle, and most content that could live in a separate reference (full matrix, rules, examples) is inlined; this fits 'some structure, references not clearly signaled/inline content that should be separate' rather than the well-split 4.

3 / 5

Total

16

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-formed description that clearly states the capability and provides explicit, natural trigger guidance. It is specific, complete, and distinct from other skills.

DimensionReasoningScore

Specificity

Names the domain ('SLA deadlines for support tickets') and concrete inputs ('customer tier and urgency'), listing a clear action; coverage is good but not fully comprehensive of all calculation sub-tasks, fitting the 'several specific actions; minor gaps' anchor and below the comprehensive 5.

4 / 5

Completeness

Explicitly answers both 'what' (calculate SLA deadlines) and 'when' via a concrete 'Use when...' clause with multiple trigger phrases, matching the top anchor; it is not a 4 because the trigger guidance is concrete and specific rather than vague.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'determining response deadlines', 'checking SLA compliance', and 'SLA, deadline, or response time requirements' give good keyword coverage; a few common synonyms are absent, so it sits above the 'some relevant keywords' (3) anchor but short of fully comprehensive (5).

4 / 5

Distinctiveness Conflict Risk

A clear SLA/deadline niche with distinct triggers and minimal overlap with unrelated skills; it does not fall to 4 since the triggers are specific enough to avoid misactivation.

5 / 5

Total

18

/

20

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.

Validation — 15 / 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

Path

lesson-04-claude-code-config/exercise/solution/.claude/skills/sla-calculation/SKILL.md

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.