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

59%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.gemini/skills/harden/SKILL.md

Quality

Discovery

92%

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 strong skill description that clearly communicates specific capabilities and includes explicit trigger guidance. It covers both what the skill does and when to use it with natural language triggers. The only minor weakness is potential overlap with general code quality or frontend development skills, though the specific focus on resilience and hardening helps differentiate it.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: error handling, i18n support, text overflow handling, edge case management, and making interfaces production-ready. These are distinct, actionable capabilities.	3 / 3
Completeness	Clearly answers both 'what' (improve resilience through error handling, i18n, text overflow, edge cases) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios.	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'harden', 'production-ready', 'edge cases', 'error states', 'overflow', 'i18n'. These cover common variations of how users would describe this need.	3 / 3
Distinctiveness Conflict Risk	While 'harden' and 'production-ready' are fairly distinct triggers, terms like 'error handling' and 'edge cases' could overlap with general code quality or testing skills. The UI/interface focus helps but isn't strongly differentiated from general frontend skills.	2 / 3
	Total	11 / 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 attempts to be a comprehensive hardening guide but suffers from being too broad and verbose, covering many topics Claude already knows well (basic CSS, form validation, accessibility fundamentals). The content would benefit significantly from being restructured as a concise overview with references to detailed sub-files, and from focusing on non-obvious patterns and project-specific conventions rather than general web development best practices.

Suggestions

Split content into separate files (e.g., I18N.md, ERROR_HANDLING.md, ACCESSIBILITY.md, PERFORMANCE.md) and make SKILL.md a concise overview with clear links to each.

Remove explanations of concepts Claude already knows (basic CSS overflow, what UTF-8 is, what debouncing is) and focus on non-obvious patterns, project-specific conventions, or decision frameworks.

Add an explicit workflow with validation checkpoints, e.g., 'Run accessibility audit after changes → fix issues → re-audit → only then move to next hardening dimension.'

Replace checklist-style bullet points with more executable examples or decision trees that guide Claude to the right approach based on context.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~300+ lines, covering many topics Claude already understands well (CSS overflow, basic form validation, accessibility fundamentals, debouncing). Much of this is general web development knowledge that doesn't need to be spelled out in such detail. Sections like 'Graceful degradation' and 'Browser compatibility' list basic concepts without adding novel insight.	1 / 3
Actionability	The skill provides some concrete, executable code snippets (CSS truncation, Intl API usage, debounce examples, HTML input constraints), but much of the content is checklist-style bullet points that describe what to do rather than showing exactly how. Many sections are lists of considerations rather than copy-paste-ready implementations.	2 / 3
Workflow Clarity	The skill has a loose workflow structure (Assess → Harden across dimensions → Verify), but lacks explicit validation checkpoints between steps. The 'Verify Hardening' section at the end is a checklist but doesn't define a feedback loop for fixing issues found during verification. For a skill involving potentially destructive UI changes, the absence of explicit validate-fix-retry loops caps this at 2.	2 / 3
Progressive Disclosure	The entire skill is a monolithic wall of content with no references to external files. Given the breadth of topics covered (i18n, error handling, accessibility, performance, testing), this content should be split across multiple files with the SKILL.md serving as an overview. Instead, everything is inlined, making it overwhelming and hard to navigate.	1 / 3
	Total	6 / 12 Passed

Validation

100%

Warnings & errors only

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: pbakaus/impeccable
Commit: db1add7

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.