CtrlK
BlogDocsLog inGet started
Tessl Logo

figma-code-connect

Creates and maintains Figma Code Connect template files that map Figma components to code snippets. Use when the user mentions Code Connect, Figma component mapping, design-to-code translation, or asks to create/update .figma.ts or .figma.js files.

74

Quality

92%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with a clear, validated workflow and clean progressive disclosure to real reference files. Its main weakness is conciseness: several icon/INSTANCE_SWAP examples and a reference table are repeated, and the inline quick reference duplicates the Step 5 mapping table.

Suggestions

Consolidate the repeated INSTANCE_SWAP/icon example (it appears in the property-mapping section, the nested-component example, and Rules and Pitfalls) into one canonical illustration and reference it from the other locations.

Merge or remove the 'Inline Quick Reference' instance.* table where it duplicates the Step 5 property-mapping table, keeping only genuinely new signatures such as findConnectedInstances and findLayers.

Trim the duplicated exhaustive-variant guidance — the getEnum 'must list every value' rule is explained in both the exhaustive-variant-handling section and Rules and Pitfalls; state it once.

DimensionReasoningScore

Conciseness

The body is dense and largely avoids explaining concepts Claude already knows, but the icon/INSTANCE_SWAP example recurs in several near-duplicate forms (e.g. lines 213-220, 285-296, 436-449) and the inline Quick Reference table partially duplicates the Step 5 property-mapping table, so it could be tightened.

2 / 3

Actionability

It provides fully executable TypeScript templates, specific MCP tool calls with named parameters, a complete end-to-end worked example, and copy-paste-ready method tables and signatures.

3 / 3

Workflow Clarity

The six steps are clearly sequenced, Step 6 is an explicit validation checkpoint with a checklist, Step 4 requires user confirmation before proceeding, and batch/destructive cases include feedback loops (fix and re-validate, ask user to confirm).

3 / 3

Progressive Disclosure

SKILL.md acts as an overview and points to real, one-level-deep, well-signaled references — api.md and advanced-patterns.md both exist and are clearly cited — keeping the full API reference and advanced nesting out of the inline body.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong across all dimensions: it states concrete capabilities, includes natural and varied trigger terms, explicitly covers both 'what' and 'when', and occupies a clear niche unlikely to conflict with other skills. Third-person voice is used correctly throughout.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Creates and maintains Figma Code Connect template files that map Figma components to code snippets' — naming specific actions rather than abstract language.

3 / 3

Completeness

It explicitly answers both what ('Creates and maintains Figma Code Connect template files...') and when ('Use when the user mentions Code Connect, Figma component mapping...'), with explicit trigger guidance.

3 / 3

Trigger Term Quality

It covers natural trigger terms users would say — 'Code Connect, Figma component mapping, design-to-code translation' — plus concrete file extensions '.figma.ts or .figma.js', giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

It targets a clear niche (Figma Code Connect templates) with distinct triggers and specific file extensions, making it unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (528 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
Devin-AXIS/iPolloWork
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.