CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gitbutler-ui

Use when changing what users see in an app built on `@gitbutler/but-ui-react`, such as 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

97%

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

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 tightly written, repo-specific skill that tells the agent exactly where to look (paths, components, commands), how to work (copy the closest existing example), and how to verify (light/dark screenshot), while correctly pushing detail into the project's own design pages and story files rather than inlining it. The only soft spot is that the working sequence is conveyed by section order rather than explicit steps, which costs it a point on workflow clarity.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence ("find the closest thing that already exists and copy it... not a gate to clear before starting") and every section carries project-specific knowledge Claude could not know: component inventory, source paths, the stories/`Default` convention, DESIGN.md locations, and the demos command. No padding or explanation of generally known concepts, matching the 'every token earns its place' anchor.

5 / 5

Actionability

Guidance is concrete and executable throughout: exact paths (`packages/but-ui-react/src/`, `web/node_modules/@gitbutler/but-ui-react/src/`), a copy-paste command (`pnpm -F @gitbutler/but-ui-react demos`), a named component inventory (Button, Popup, Select, Field, Checkbox, Switch, Tooltip, EmptyState, Snackbar, Toasts, Banner), and a precise copy-the-closest-story procedure. As an instruction-only skill whose guidance is fully actionable, the absence of inline code is not penalized.

5 / 5

Workflow Clarity

A clear sequence is present through section order — start from the library, copy the closest example and adapt, consult design pages, apply wording rules, then verify — and an explicit check step exists ("Look at the result in light and dark, and keep one screenshot"). It sits at level 4 rather than 5 because the sequence is implied by section order rather than explicitly enumerated, and there is no error-recovery guidance; it is above level 3 because the ordering and a validation checkpoint are unambiguous and no destructive/batch operations are involved.

4 / 5

Progressive Disclosure

The skill is a short (~45 content lines), well-sectioned overview with no bundle files, and it appropriately delegates bulk detail to existing one-level-deep repo resources (each component's stories, the `DESIGN.md` index and its `design/` pages, `AGENTS.md`) with explicit guidance to load selectively ("Read the pages for what you are building, not all of them"). This matches the clear-overview with well-signaled references anchor.

5 / 5

Total

19

/

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: it names a precise niche via the library and app identifiers, enumerates concrete UI-change actions that double as natural trigger terms, opens with an explicit 'Use when' clause, and closes with a negative scope boundary. It is concise, in the expected voice, and free of fluff or over-claims.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "adding or restyling a component, modal, form, list, empty state or toast, or writing the words on screen" — which comprehensively covers the visible-UI change space for this domain. It matches the anchor for multiple specific concrete actions with comprehensive coverage, not the level 4 anchor, which is reserved for lists with minor coverage gaps.

5 / 5

Completeness

Both 'what' (changing what users see: adding/restyling components, modals, forms, lists, empty states, toasts, writing on-screen words) and 'when' (explicit "Use when changing what users see in an app built on `@gitbutler/but-ui-react`...") are clearly answered with concrete trigger phrases, plus an explicit negative boundary ("Not for logic, data or backend work"). This matches the anchor that explicitly answers both what and when with concrete triggers.

5 / 5

Trigger Term Quality

Natural trigger terms a user would actually say are well covered: "component", "modal", "form", "list", "empty state", "toast", "restyling", and "writing the words on screen" (i.e., copy/text). This spans the common synonyms (modal≈dialog, restyling≈styling/theming, words on screen≈copy/labels), matching the comprehensive-coverage anchor rather than level 4's 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

The niche is sharply defined by the library name (`@gitbutler/but-ui-react`), a concrete app example ("the but.dev web app"), and an explicit exclusion clause ("Not for logic, data or backend work, even inside a UI file") that prevents mis-triggering. Clear niche with distinct triggers and minimal conflict risk, matching the level 5 anchor.

5 / 5

Total

20

/

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/but-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.