CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gitbutler-ui

Use when changing what users see in an app built on `@gitbutler/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

92%

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.

The body is an exemplary lean instruction skill: concrete pointers instead of tutorials, explicit where-to-look and what-to-check guidance, and well-signaled one-level-deep references into the library and design pages. The only soft spot is a merely implied rather than explicitly sequenced workflow.

DimensionReasoningScore

Conciseness

The ~55-line body is lean with no padding and no explanation of concepts Claude already knows; every line carries repo-specific knowledge (component inventory, source paths, stories convention, demos command).

5 / 5

Actionability

Guidance is fully executable for an instruction-only skill: exact source paths in both repos, a copy-paste command (`pnpm -F @gitbutler/ui-react demos`), specific example mapping ("a confirmation is Modal's, a picker Popup's or PickerDialog's"), and a concrete fallback with what to say in the PR description.

5 / 5

Workflow Clarity

The sections imply a clear order (find the closest existing thing, read the design pages, follow the words guidance, check the result) and "Check it" is an explicit validation checkpoint (light and dark, keep a screenshot). It falls short of 5 because there is no explicit sequenced checklist or error-recovery feedback loop.

4 / 5

Progressive Disclosure

A short single-file skill with no bundle files, organized into clear sections; all detail (library source, JSDoc, stories, DESIGN.md, per-topic design pages) is one level deep, clearly signaled, and gated by "each saying when to read it".

5 / 5

Total

19

/

20

Passed

Description

87%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 strong description: it states concrete actions, an explicit "Use when..." trigger scoped to a named library and app, and a clear negative boundary. Coverage of action types and natural synonyms has only minor gaps.

DimensionReasoningScore

Specificity

"adding or restyling a component, modal, form, list, empty state or toast, or writing the words on screen" lists several concrete actions with enumerated artifact types, but the "such as" framing marks the list as exemplary rather than comprehensive (e.g., removal, layout or theming changes are not named).

4 / 5

Completeness

The "Use when changing what users see..." clause explicitly answers when, the enumerated actions explicitly answer what, and the closing exclusion ("Not for logic, data or backend work") sharpens both with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural terms users would say are well covered (component, modal, form, list, empty state, toast, words on screen, but.dev), but a few common synonyms are missing, e.g. "copy", "text", "styling" or "design".

4 / 5

Distinctiveness Conflict Risk

The description is pinned to a specific library and app (`@gitbutler/ui-react`, the but.dev web app) and explicitly excludes logic, data and backend work, giving it a clear niche with minimal conflict risk.

5 / 5

Total

18

/

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.