CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

harden

Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.

Quality

78%

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 ./templates/skills/impeccable/harden/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-structured and actionable, with concrete code for overflow, RTL, Intl formatting, input constraints, and reduced motion, plus a real verification checklist. Its weaknesses are token efficiency — the same extreme-input/i18n guidance is repeated across the Assess, Testing, and Verify sections — and the absence of any progressive disclosure, with all ~350 lines inlined where several dimensions could live in reference files.

Suggestions

Consolidate the redundant testing guidance: 'Assess Hardening Needs', 'Testing Strategies', and 'Verify Hardening' repeat the same extreme-input/i18n/network checks — merge into a single assess section and a single verification checklist to cut token load.

Split the deep-dive dimensions (i18n, Accessibility Resilience, Performance Resilience) into reference files (e.g. references/i18n.md, references/accessibility.md) and keep SKILL.md as an overview, so detail loads only when relevant.

Tighten vague checklist items like 'Handle race conditions' and 'Performance optimization' into concrete patterns (e.g. the AbortController-on-unmount cleanup you already show under Memory leaks), and define or import the debounce/throttle helpers the code snippet assumes.

DimensionReasoningScore

Conciseness

Mostly useful but noticeably padded: 'Test with extreme inputs' reappears as 'Test with extreme data' and again as 'Try names with 100+ characters'; i18n guidance is covered three times (Assess, Hardening Dimensions, Verify); and lists of known concepts ('No items in list / No search results / No notifications') add little. Not score 4 because the cross-section redundancy is more than minor trimming; not score 2 because genuinely non-obvious specifics (German ~30% expansion, 30-40% space budget, min-width: 0 for flex overflow) earn their place.

3 / 5

Actionability

Provides mostly executable guidance: concrete CSS for truncation/line-clamp/flex overflow, JSX i18n examples, Intl.DateTimeFormat/NumberFormat calls, an HTML constraint example with aria-describedby, and a prefers-reduced-motion block. Falls short of score 5 because some items stay vague ('Handle race conditions', 'Conflict resolution', 'Performance optimization') and `debounce(handleSearch, 300)` assumes an undefined helper.

4 / 5

Workflow Clarity

A clear assess → harden → test → verify sequence, with the 'Verify Hardening' section acting as an explicit checklist ('Click submit 10 times rapidly', 'Disable internet, throttle connection'). Not score 5 because there is no feedback loop for what to do when verification fails, and the sequence is implied by section order rather than an explicit numbered workflow; not score 3 because the verification checkpoints are present and concrete.

4 / 5

Progressive Disclosure

Section structure is well-organized (consistent headers and subsections), but ~350 lines are inlined in a single SKILL.md with zero bundle files; subtopics like i18n, accessibility resilience, and performance clearly belong in separate reference files. Matches the score-3 anchor (content that should be separate is inline) rather than 2 because internal structure and navigation are good, and not 4 because no content is split out at all.

3 / 5

Total

14

/

20

Passed

Description

83%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 description: third-person voice, concrete capability areas, and an explicit 'Use when...' clause with natural trigger phrases that clearly answer both what the skill does and when to use it. The only weaknesses are minor — a few missing synonyms in the trigger list and omission of the accessibility/performance dimensions the body actually covers.

DimensionReasoningScore

Specificity

The description lists several concrete capability areas — 'error handling, i18n support, text overflow handling, and edge case management' — which is more than the 1-2 actions of a score-3 anchor. It falls short of comprehensive (score 5) because the body also covers accessibility and performance resilience, which the description omits.

4 / 5

Completeness

It explicitly answers both: what ('Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready.') and when ('Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.'), with concrete trigger phrases — a direct match for the score-5 anchor.

5 / 5

Trigger Term Quality

'harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues' provides good natural-phrase coverage a user would actually say. Not score 5 because common synonyms such as 'robust', 'defensive', or 'graceful degradation' are missing; not score 3 because the term set is broad and domain-appropriate rather than sparse.

4 / 5

Distinctiveness Conflict Risk

The UI-hardening niche ('interface resilience', 'text overflow', 'i18n', 'production-ready') is mostly distinct with clear triggers. Minor overlap risk remains with general coding/error-handling skills since 'handle edge cases' and 'add error states' could apply to non-interface code, keeping it below a score-5 clear-niche anchor.

4 / 5

Total

17

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

fengshao1227/ccg-workflow

Path

templates/skills/impeccable/harden/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.