CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gitbutler-ui

Use when changing what users see in an app built on `@gitbutler/ui-react` — Lite, the but.dev web app — adding or restyling a component, modal, form, list, empty state or toast, or writing the words on screen. Not for logic, data or backend work, even inside a UI file.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A lean, project-specific guide that tells the agent exactly where to look, what to copy, and how to verify the result. It would be even stronger with a brief recovery note for when the visual check fails.

DimensionReasoningScore

Conciseness

"find the closest thing that already exists and copy it" assumes Claude's competence; every section carries only project-specific knowledge (component names, exact paths, commands) with no padding of concepts Claude already knows.

5 / 5

Actionability

Exact paths ("packages/ui-react/src/", "web/node_modules/@gitbutler/ui-react/src/"), named tools (`docs-show`, the chromatic manifest URL) and a copy-paste command ("pnpm -F @gitbutler/lite demos") make the guidance fully executable, with a concrete fallback ("build the smallest thing that works and say so in the PR description").

5 / 5

Workflow Clarity

Sections run in workflow order (library → design pages → words → check) and end with an explicit checkpoint ("Look at the result in light and dark, and keep one screenshot"), but there is no recovery guidance if the check fails, so it falls short of the feedback-loop anchor 5.

4 / 5

Progressive Disclosure

The body is an overview deferring detail to one-level-deep, well-signaled sources (library `src/`, the `DESIGN.md` index pages, Storybook) with explicit read-what-you-need guidance ("Read the pages for what you are building, not all of them"); no bundle files exist and nothing is inlined that belongs elsewhere.

5 / 5

Total

19

/

20

Passed

Description

92%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 tightly scoped description that names the target apps, enumerates concrete UI actions, and states both when to use it and when not to. The only gap is a handful of missing natural synonyms (button, dialog, dropdown) among trigger terms.

DimensionReasoningScore

Specificity

"adding or restyling a component, modal, form, list, empty state or toast, or writing the words on screen" lists multiple concrete actions with explicit exclusions ("Not for logic, data or backend work"), matching the comprehensive-coverage anchor rather than the 4 anchor's minor gaps.

5 / 5

Completeness

"Use when changing what users see in an app built on `@gitbutler/ui-react` — Lite, the but.dev web app" is an explicit when with concrete trigger scope, the enumerated restyling/copy actions answer the what, and the negative scope ("Not for logic, data or backend work") reinforces both.

5 / 5

Trigger Term Quality

"component", "modal", "form", "toast", "empty state" are natural terms users would say, but common synonyms like "button", "dialog", "dropdown" or "styling" are absent — good coverage with a few natural terms missing, short of the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche is precise (apps built on `@gitbutler/ui-react`, Lite and but.dev) and "Not for logic, data or backend work, even inside a UI file" explicitly fences off adjacent work, giving minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

gitbutlerapp/gitbutler

Path

packages/ui-react/skill/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.