harden

Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready.

1.27x

Quality

62%

Does it follow best practices?

Impact

83%

1.27x

Average score across 6 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./archived/legacy-companion/.agents/skills/harden/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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 concrete code examples and good section structure, but it is verbose from repeated test lists and monolithic with no progressive disclosure into reference files. Adding a validation feedback loop and splitting detail into references would raise the weaker dimensions.

Suggestions

De-duplicate the repeated extreme-input/error/i18n test lists (Assess Hardening Needs, Testing Strategies, and Verify Hardening all restate the same items) into one shared checklist.

Add explicit validation/feedback checkpoints — e.g. after hardening, run axe/accessibility and visual-regression checks, fix flagged issues, then re-verify before proceeding.

Move detailed CSS overflow, i18n, and error-state code patterns into reference files (e.g. references/i18n.md, references/css-patterns.md) and link them from SKILL.md to break up the monolithic body.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and accurate but repeats the same test-case lists (long text, emoji, RTL, CJK, network, large datasets, empty states) across Assess, Testing Strategies, and Verify sections, so it could be tightened considerably.	2 / 3
Actionability	It provides fully executable CSS, JSX, and JavaScript examples (ellipsis/clamp, Intl formatting, debounce/throttle) plus concrete per-status-code handling, matching the copy-paste-ready anchor.	3 / 3
Workflow Clarity	A loose sequence exists (Assess → Harden → Test → Verify) but there are no explicit validation checkpoints or validate-fix-retry feedback loops, only a terminal test list.	2 / 3
Progressive Disclosure	Sections are clearly organized, but the ~350-line body is monolithic with all CSS/i18n/error patterns inline and no external reference files split out, so content that should be separate remains inline.	2 / 3
	Total	9 / 12 Passed

Description

60%Weight 40%Scale 1-3

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 specific about what the skill does but omits any explicit when-to-use trigger guidance. Adding a 'Use when...' clause with natural user terms would lift completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when hardening UIs against edge cases, errors, i18n issues, or text overflow before production release.'

Surface natural trigger terms a user would actually say (e.g. 'production-ready', 'edge cases', 'error handling', 'RTL', 'text overflow') rather than only technical phrasing like 'i18n'.

Dimension	Reasoning	Score
Specificity	It lists multiple concrete actions — 'better error handling, i18n support, text overflow handling, and edge case management' — matching the anchor for naming several specific actions rather than vague language.	3 / 3
Completeness	It clearly states what the skill does but lacks any 'Use when...' clause or equivalent explicit trigger guidance, so when-to-use is only implied, capping completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Terms like 'error handling', 'i18n', and 'text overflow' are relevant but 'i18n' is somewhat technical and there are no common user-facing variations (e.g. 'production-ready', 'edge cases') nor a trigger list.	2 / 3
Distinctiveness Conflict Risk	'Interface resilience' and 'edge case management' carve a niche but overlap with general frontend/coding skills, and without explicit triggers it could fire for the wrong skill.	2 / 3
	Total	9 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: The-Vibe-Company/companion
Path: archived/legacy-companion/.agents/skills/harden/SKILL.md
Commit: 90804d3

Reviewed: 18 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.