CtrlK
BlogDocsLog inGet started
Tessl Logo

figma-automation

Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas.

76

2.34x
Quality

65%

Does it follow best practices?

Impact

96%

2.34x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/figma-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 content is highly actionable and well-structured, but redundant pitfall sections and missing validation checkpoints for write/batch operations hold it back from the top band. Tightening duplication and adding explicit verification steps would materially improve it.

Suggestions

De-duplicate the "Known Pitfalls" section — file-type support and node-ID format are already covered in per-workflow pitfalls and Common Patterns; keep one canonical location.

Add explicit validation checkpoints for write/batch operations (verify a comment was posted; check the image-render map for null entries before downloading).

Optionally move the Quick Reference table and detailed per-workflow parameters into a bundled reference file to shorten SKILL.md toward an overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient operational detail Claude would not already know, but the "Known Pitfalls" section duplicates per-workflow pitfalls (file-type support, node-ID dash→colon) and the Quick Reference repeats tool slugs, creating noticeable redundancy.

3 / 5

Actionability

Concrete tool slugs with explicit parameters (file_key, comma-separated ids, depth, scale 0.01-4.0, format options) and per-step pitfalls give mostly executable guidance; the minor gap is the absence of copy-paste MCP tool-call code blocks.

4 / 5

Workflow Clarity

Workflows are clearly numbered with [Prerequisite]/[Required]/[Optional] markers and the Setup validates the connection, but write/batch operations (adding comments, image export) lack explicit validate-and-retry checkpoints, capping this at 3 per the feedback-loop guideline.

3 / 5

Progressive Disclosure

A single well-organized file with clear sections (Prerequisites, Setup, five Core Workflows, Common Patterns, Quick Reference) and no nested references; no bundle files exist, so structure is judged on sectioning, which is good with minor redundancy that could be split out.

4 / 5

Total

14

/

20

Passed

Description

70%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.

The description is specific and clearly niche-targeted, but it omits an explicit "when to use" trigger clause, which limits completeness. Adding a Use-when clause and verb-led actions would lift it into the top band.

Suggestions

Add an explicit "Use when..." trigger clause (e.g., "Use when working with Figma design files, exporting assets, or extracting design tokens") to raise completeness above 3.

Include natural user phrasing and synonyms (frames, styles, .fig files) to broaden trigger-term coverage.

Lead with verbs (extract, export, render, comment on) instead of a noun list for sharper specificity.

DimensionReasoningScore

Specificity

The description lists five concrete domains — "files, components, design tokens, comments, exports" — but presents them as noun objects rather than verb-led actions, which is slightly less concrete than the anchor-5 verb-driven example.

4 / 5

Completeness

It states a clear "what" ("Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports") but has no "Use when..." trigger clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms like "Figma", "design tokens", "components", "comments", and "exports" give good keyword coverage, though common synonyms users might say (frames, styles, .fig) are missing.

4 / 5

Distinctiveness Conflict Risk

The pairing of "Figma" with "Rube MCP (Composio)" carves a clear, tool-specific niche with minimal overlap risk against other skills.

5 / 5

Total

16

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
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.