CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

design-tokens

Use when pulling design tokens from Figma into `packages/but-ui`, regenerating `tokens.css`, or reviewing a token change: sync/export/update tokens, a Figma variable was added, renamed or changed, or `pnpm check` says tokens.css is stale. Not for using tokens in components; that is the gitbutler-ui skill.

Quality

95%

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

96%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 exemplary workflow skill: dense with non-derivable project constraints, fully executable commands at every step, and explicit validation checkpoints with stop conditions and error-recovery loops. The only structural headroom is that the alternate export routes and naming rules could eventually be split into reference files as the skill grows.

DimensionReasoningScore

Conciseness

Every sentence carries project-specific constraints Claude could not infer — "Figma's variables REST API is Enterprise-only, so the CLI's own fetch answers `403`", "A `use_figma` result can't carry it: it caps at 48 KB" — with zero padding and no explanation of concepts Claude already knows. This is anchor 5's 'lean and efficient; every token earns its place'.

5 / 5

Actionability

Copy-paste-ready commands throughout: `npx tokens-bruecke@latest --input snapshot.json -c figma-export.config.json -o tokens/json --split-by-collection`, `git diff -U0 tokens/json | grep ... | grep -v createdAt`, `node scripts/diff-css-vars.mjs "$TMPDIR/tokens-before.css" tokens/tokens.css`, `pnpm --filter @gitbutler/but-ui-react check:tokens`, plus a concrete REST URL with header for the snapshot fetch. Fully executable and covering the common cases plus alternate routes, matching anchor 5.

5 / 5

Workflow Clarity

A clearly numbered 5-step pipeline with explicit validation and stop conditions: step 2's diff check ("No output: `git checkout -- tokens/json`, tell the user Figma has no changes, and stop"), step 3's diff report with interpretation guidance, and step 4's broken-reference check with a recovery path (`scripts/rename-tokens.mjs` reading `token-map.json`). Error handling is explicit (403 → "Stop and ask; never hand-edit the JSON instead"), satisfying anchor 5's feedback loops for a batch operation.

5 / 5

Progressive Disclosure

Well-organized numbered sections with a clearly signaled one-level pointer ("The package README has the pipeline in full"), and no bundle files exist to reference. It sits at anchor 4 rather than 5 because at ~95 dense lines the alternate export routes (Enterprise CLI, Figma agent, PR server) and the CSS naming rules are candidates for extraction into reference files, leaving minor organization headroom.

4 / 5

Total

19

/

20

Passed

Description

95%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 excellent description: it states a concrete what, an explicit 'Use when' with multiple concrete trigger phrasings including the exact staleness error, and an explicit exclusion clause that prevents triggering for the related gitbutler-ui skill. Only a minor coverage gap (downstream fixes and commit steps unmentioned) keeps specificity from the top anchor.

DimensionReasoningScore

Specificity

Quotes "pulling design tokens from Figma into `packages/but-ui`, regenerating `tokens.css`, or reviewing a token change: sync/export/update tokens" — several concrete, domain-specific actions. It falls at anchor 4 rather than 5 because coverage has minor gaps (e.g., fixing downstream references to removed/renamed variables and committing are not mentioned), and is clearly above anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

Explicitly answers both questions: the what ("pulling design tokens from Figma into `packages/but-ui`, regenerating `tokens.css`, or reviewing a token change") and the when ("Use when... a Figma variable was added, renamed or changed, or `pnpm check` says tokens.css is stale"). Concrete trigger phrases plus an explicit negative boundary ("Not for using tokens in components") place it squarely at anchor 5, above anchor 4's 'when could be more specific'.

5 / 5

Trigger Term Quality

Covers the natural terms a user would actually say: "design tokens", "Figma", "sync/export/update tokens", "a Figma variable was added, renamed or changed", and the exact failure message "`pnpm check` says tokens.css is stale". This matches anchor 5's comprehensive natural-term coverage including tool and file names; no common synonym or trigger variant is missing.

5 / 5

Distinctiveness Conflict Risk

A clear niche (Figma variables → but-ui token pipeline) with distinct triggers, and it explicitly disambiguates from the nearest sibling: "Not for using tokens in components; that is the gitbutler-ui skill". Minimal conflict risk, matching anchor 5.

5 / 5

Total

19

/

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

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository

gitbutlerapp/gitbutler

Path

.agents/skills/design-tokens/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.