Skip to content
SkillModel-led1,082 tokens in use

Break

Renders one component you choose under every scenario that can reach it on a temporary harness page, then marks what visibly broke.

12,497 stars on the repository MIT Licensejakubkrehel/skills · skills/break
npx skills add jakubkrehel/skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Break costs

24tokens idle
1,082tokens in use
2,036tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Fair
  • Frontmatter8/15
  • Structure8/25
  • Examples0/15
  • Output5/15
  • Size15/15
  • Resources7/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity96
  • Maintenance52
  • Community48
  • Maturity24
  • Momentum40

Break is a user-invoked agent skill that stress tests a single UI component. It reads the component’s props and data, keeps only the scenarios that can occur in production, and renders the real component once per scenario in a single column on a scratch route, so you can scroll through every case.

The page is the report. Each break is noted under its scenario and named in the vocabulary of the sibling skill that owns the fix, and a run where everything survived is a complete result.

What You Get

  • A scratch route in your app that renders the real component once per scenario, each labeled, with breaks noted under their label
  • A one-line list of scenarios kept and axes dropped, so a wrong inference is cheap to catch
  • A findings table listing the scenario, what was observed and the owning skill, with broken scenarios first
  • Scenario sets such as empty, one word, several sentences and one unbreakable string, plus zero, one and ten times the realistic item count
  • The page left running until you say you are done, and removal of the route and fixtures on request

Common Use Cases

  • Checking a button, badge or card against long, empty and translated labels
  • Finding how a list component behaves with zero items, one item and a very large count
  • Seeing whether a form field survives a 320px container and a very wide one
  • Confirming loading, error and disabled states do not collapse or lose contrast

What Makes It Unique

It observes and issues no verdict, and it isolates the component on purpose to test whether it defends itself against worst-case content. It adds no styles, fonts or simulated themes of its own, because a component observed under those is a different component. Dark mode, zoom and reduced motion are left for you to toggle while viewing.

Under The Hood

The skill is a SKILL.md and a scenario reference, with no scripts. The agent writes new files in your project: a scratch route and fixture data that import your real component. It runs your dev server and opens the page in a browser if one is available, otherwise it hands you the URL to check. Nothing is fetched from the web. The harness never connects to live data or production state, and the files are deleted when you ask.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers