CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

figma-token-sync

Bidirectionally sync CSS custom properties with Figma variables — push local tokens to Figma, pull Figma changes to CSS, and diff for CI drift detection. Use when "syncing Figma tokens", "Figma variables", "design token sync", or "CSS to Figma".

Quality

84%

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

68%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 well-structured, concrete, and information-dense across all three sync operations, with proper use of an external schema reference. Its main weaknesses are the lack of validation checkpoints around the batch PUSH operation and references to helper functions that have no implementation in the bundle.

Suggestions

Add explicit validation checkpoints to the PUSH workflow: run DIFF first to preview pending changes, and verify the Figma API response (variable counts, assigned IDs) before writing the lock file — this is a batch write to a shared design file and currently has no validation gate.

Either ship implementations for `parseCSSTokens()`, `classifyToken()`, and `hexToFigmaColor()` in a scripts/ directory (with paths in the body) or explicitly state Claude must implement them from the described rules — they are currently named as if they already exist.

Remove the Quick Reference metadata table ("Complexity: High | 4 projects") at the top of the body; it duplicates frontmatter information and adds tokens without operational value.

DimensionReasoningScore

Conciseness

The body is dense and operational (API endpoints, config examples, type-mapping tables) with almost no explanation of concepts Claude already knows. However, the Quick Reference table ("Complexity | High | 4 projects") duplicates frontmatter metadata and the four-tier parsed-token JSON example could be trimmed, so it fits anchor 4's 'minor instances that could be trimmed' rather than anchor 5's 'every token earns its place'.

4 / 5

Actionability

Guidance is mostly executable: concrete API endpoints with auth headers, request-body structure, rate-limit policy, naming conventions, lock-file format, and DIFF exit codes. It falls short of anchor 5 because functions like `parseCSSTokens(cssString)`, `classifyToken(name, value)`, and `hexToFigmaColor()` are referenced as if they exist, yet no scripts/ directory or implementation is provided in the bundle.

4 / 5

Workflow Clarity

Each of the three operations has a clearly numbered, well-sequenced step list, but PUSH is a batch write to a shared Figma file with no pre-push validation checkpoint (no dry-run or DIFF-first preview) and no post-push verification beyond writing the lock file after 'a successful push'. Per the rubric's batch-operation cap, missing validation gates cap this at anchor 3 even though the sequences themselves are clear.

3 / 5

Progressive Disclosure

The config schema is appropriately split into a real, clearly signaled one-level-deep reference (`references/figma-config-schema.md`) with only a minimal example inlined. It is not anchor 5 because the body is a fairly monolithic full instruction set — detail like the complete lock-file format and troubleshooting matrix lives inline with only one external reference, fitting anchor 4's 'most content appropriately placed; minor organization gaps'.

4 / 5

Total

15

/

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 strong description: it states all three concrete operations (push, pull, diff for CI), includes an explicit 'Use when' clause with natural Figma-anchored trigger phrases, and occupies a clear niche with minimal conflict risk. The only weakness is slightly incomplete trigger synonym coverage.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering all three operations comprehensively: "push local tokens to Figma, pull Figma changes to CSS, and diff for CI drift detection". There are no coverage gaps, so it matches the anchor-5 example rather than anchor 4's 'minor gaps in coverage'.

5 / 5

Completeness

It explicitly answers both what (bidirectional sync with push/pull/diff) and when ("Use when 'syncing Figma tokens'...") with concrete trigger phrases, mirroring the anchor-5 good example. Anchor 4 would require the 'when' to be less explicit, which is not the case.

5 / 5

Trigger Term Quality

Trigger phrases "syncing Figma tokens", "Figma variables", "design token sync", "CSS to Figma" give good keyword coverage across both directions. It falls short of anchor 5 because common natural variations like "design tokens" generically, "Figma to CSS", or "push tokens to Figma" are missing.

4 / 5

Distinctiveness Conflict Risk

Every trigger is Figma-anchored and the CSS↔Figma variable sync niche is distinct; sibling skills like brand-css-generator produce CSS rather than sync it, so conflict risk is minimal. It fits anchor 5 better than anchor 4's 'minor overlap risk with closely related skills'.

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

paolomoz/skills

Path

skills/figma-token-sync/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.