CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

graceful-degradation

Graceful Degradation with Helpful Messages

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/graceful-degradation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 body is a strong, tight implementation of the pattern: complete executable code with caching and timeouts, a reusable message template, and clear DO/DON'T guidance. Its only real weakness is the non-actionable 'Source Sessions' provenance section and the absence of a single explicit ordered workflow statement.

DimensionReasoningScore

Conciseness

The body is efficient: terse DO/DON'T lists, one complete code example, and a short generalizable template, with no explanation of concepts Claude already knows. The one trimmable blemish is the 'Source Sessions' section (~4 lines of provenance metadata with no instructional value), which keeps it below the lean anchor at 5 but above 'some unnecessary explanation' at 3.

4 / 5

Actionability

The TypeScript example is fully executable and copy-paste ready — TTL-cached availability check with AbortSignal timeout, concrete fallback message construction with install/start/verify steps — and the Fallback Message Template generalizes the pattern beyond the single LMStudio case, covering the common use cases.

5 / 5

Workflow Clarity

The sequence (check availability early → cache result → emit actionable message → continue with reduced functionality) is clear and demonstrated end-to-end in the example code, but it is distributed across the Pattern section, DO list, and code rather than presented as one explicit ordered workflow. Not a destructive or batch operation, so no validation cap applies.

4 / 5

Progressive Disclosure

No bundle files exist and all content lives in one ~85-line file with clear section headers, which is appropriate for a skill of this size. It slightly exceeds the under-50-line simple-skill threshold, and the 'Source Sessions' section is content that belongs elsewhere (or nowhere), leaving minor organization gaps that keep it at 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

28%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.

The description is a title, not a description: it names a design pattern but declares no concrete actions and provides no trigger guidance for when the skill applies. Users searching for help with an unavailable service or fallback behavior would not naturally match this text.

Suggestions

State the concrete actions in the description itself, e.g., 'Checks service availability, caches health results with a TTL, and returns actionable fallback messages explaining what is missing and how to enable it.'

Add an explicit trigger clause, e.g., 'Use when an optional service (LMStudio, local API, external endpoint) is unreachable or when adding availability checks and fallback messaging.'

Include natural user-facing phrases and synonyms — 'service unavailable', 'connection failed', 'fallback', 'health check' — so the skill surfaces when users describe these situations.

DimensionReasoningScore

Specificity

The description 'Graceful Degradation with Helpful Messages' names a domain but states no concrete actions — the actual verbs (check availability early, cache health results, provide actionable fallback messages) appear only in the body. It is above pure abstraction ('Helps with documents') but below anchor 3 because it lists no actions at all.

2 / 5

Completeness

There is no 'Use when...' clause or equivalent trigger guidance (capped at 3 by the guidelines), and the 'what' is a vague title-style noun phrase rather than a clear statement of what the skill does — matching anchor 2: 'vague what and no when'.

2 / 5

Trigger Term Quality

'Graceful Degradation' and 'Helpful Messages' are design-pattern jargon, not phrases users naturally say when they need this skill; natural triggers like 'service unavailable', 'fallback', or named services (e.g., LMStudio) are absent. It has a couple of tangentially relevant keywords but misses the natural phrasing, fitting between the jargon-only and generic-keyword anchors.

2 / 5

Distinctiveness Conflict Risk

The pattern name is somewhat specific and unlikely to be confused with most skills, but it is broad enough to overlap with general error-handling or debugging skills, matching anchor 3. It lacks the concrete, niche trigger phrases that would earn a 4 or 5.

3 / 5

Total

9

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

parcadei/Continuous-Claude-v3

Path

.claude/skills/graceful-degradation/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.