CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

break-ui

Try to break a piece of UI by feeding it worst-case data — long names, unbreakable emails, one-letter names, missing fields, huge counts, zero items, long labels, non-Latin text, emoji, extreme numbers — then render it behind a "Demo data / Worst case" toggle and report everything that broke, with the fix for each. Use when the user asks to stress-test, break, or find edge cases in a component or screen, or to "try the worst case". For visual design critique use emil-design-eng; for motion use review-animations.

Quality

96%

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

The canonical home for this skill is break-ui in emilkowalski/skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally well-crafted adversarial-testing skill: lean, concrete, and sequenced with genuine validation checkpoints and feedback loops, with a distinctive output format. Its one real defect is progressive disclosure: the workflow depends on a CATALOG.md that is absent from the bundle, leaving Phase 2 with nothing to load.

Suggestions

Include CATALOG.md in the skill bundle (e.g., at the referenced path or in references/) — Phase 2 instructs 'Load it now' but the file does not exist, breaking the workflow at that step.

Once the file exists, make the link resolve to its actual bundle location (e.g., references/CATALOG.md) so the path is verifiable.

Consider moving the failure-signature table and the truncate/wrap/clamp guidance into the catalog reference (or a second reference file) so SKILL.md stays a lean workflow overview, keeping only the most common signatures inline.

DimensionReasoningScore

Conciseness

The body is dense and operational throughout: fixes are given as terse properties (`flex-shrink: 0`, `minmax(0, 1fr)`, `Intl.PluralRules`) with no tutorials, no explanation of concepts Claude already knows, and no library comparisons. Even the persona prose earns its keep by supplying the concrete worst-case values (Aleksandra Wiśniewska-Kowalczyk, the 61-character email, 1,284 members) used later. Fits the level-5 'every token earns its place' anchor rather than level 4, which would require trimmable over-explanation.

5 / 5

Actionability

Fully executable guidance: exact test values, exact viewport checks (320px, widest layout, 200% zoom, dark mode, RTL), a concrete toggle implementation (`?data=worst` URL param, dev-only gating), a symptom→cause→fix lookup table, and a fully worked example of the required output table with severity levels. This matches 'copy-paste ready... specific examples cover the common cases'.

5 / 5

Workflow Clarity

Six clearly sequenced phases with explicit completion criteria in Phases 1 and 4 ('every rendered value is in the table...'; 'every catalog row that applies has been tried, every width and environment above has been checked'), a hard checkpoint ('Report before fixing... Fix only when asked'), and a feedback loop in Phase 6 (re-flip the toggle through every state and 'confirm each fixed break is gone', including checking the demo state for regressions). It also requires distinguishing visually-verified from inferred findings. Matches the level-5 anchor with feedback loops and checklists; the destructive/batch cap does not apply since changes are gated and verified.

5 / 5

Progressive Disclosure

The in-body structure is good and the single reference is well signaled ('pick values from [CATALOG.md](CATALOG.md). Load it now.'), but the referenced file does not exist in the bundle — there are no references/, scripts/, or assets/ directories and no CATALOG.md anywhere — so Phase 2 is unexecutable as bundled. Additionally, the 19-row failure-signature table and the truncate/wrap/clamp catalog are sizeable catalog-like detail inlined in SKILL.md. This lands between the level-2 anchor (content that belongs in separate files inlined / broken reference navigation) and level 3 (good structure, imperfect reference handling).

3 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: concrete actions with enumerated worst-case inputs, an explicit 'Use when' trigger clause with natural synonyms, and explicit redirects to adjacent skills. It uses imperative voice consistent with the reference good examples and contains no padding.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — "feeding it worst-case data", "render it behind a 'Demo data / Worst case' toggle", "report everything that broke, with the fix for each" — and itemizes the data classes (long names, unbreakable emails, zero items, emoji, extreme numbers). This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage' and exceeds the level-4 anchor's 'minor gaps', since actions, inputs, and outputs are all named.

5 / 5

Completeness

Both halves are explicit: what ("break a piece of UI by feeding it worst-case data... render it behind a toggle and report everything that broke, with the fix for each") and when ("Use when the user asks to stress-test, break, or find edge cases in a component or screen, or to 'try the worst case'"). This is the level-5 pattern — concrete what plus concrete trigger phrases — not the level-4 case of a vague or generic 'when'.

5 / 5

Trigger Term Quality

Natural user phrases are comprehensively covered: "stress-test", "break", "find edge cases", and the verbatim "try the worst case", applied to "a component or screen". File extensions don't apply to this domain, and the remaining synonyms users would say are all present, so it fits the level-5 anchor rather than level 4 ('a few natural terms missing').

5 / 5

Distinctiveness Conflict Risk

The niche is distinct (worst-case data stress-testing of rendered UI) and it actively disambiguates sibling skills: "For visual design critique use emil-design-eng; for motion use review-animations". Minimal conflict risk, matching the level-5 'clear niche with distinct triggers' anchor.

5 / 5

Total

20

/

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

englishstreetventures/osn

Path

.agents/skills/break-ui/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.