CtrlK
BlogDocsLog inGet started
Tessl Logo

figma-use-figjam

This skill helps agents use Figma's use_figma MCP tool in the FigJam context. Can be used alongside figma-use which has foundational context for using the use_figma tool.

60

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/figma-use-figjam/SKILL.md
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, actionable overview: exact syntax, named APIs, and concrete error-avoidance guidance, with a well-organized one-level-deep reference structure. The only minor gap is that batch/destructive validation feedback loops live in a referenced file rather than inline.

Suggestions

Surface a one-line validation/retry guidance for batch and destructive operations directly in the batch-modify entry so the feedback loop is visible without loading the reference.

DimensionReasoningScore

Conciseness

The body is lean and dense with operational facts (exact error strings, the precise ToolSearch 'select:' syntax, font-name gotchas) and never pads by explaining what FigJam or MCP is; every token earns its place, matching the 'Lean and efficient; assumes Claude's competence' anchor.

5 / 5

Actionability

Guidance is concrete and copy-paste-ready: the exact ToolSearch query string, named APIs to call and avoid (get_figjam, upload_assets vs figma.createImage), and the canonical load→await→mutute→return text recipe — no pseudocode, fully executable.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced with explicit checkpoints and recovery guidance (get IDs upfront via get_figjam, re-call get_figjam rather than re-running inspection scripts if an ID is missing), but the batch/destructive operations defer their validation feedback loops to the referenced batch-modify file rather than stating them inline, leaving a minor validation gap.

4 / 5

Progressive Disclosure

The SKILL.md is a concise overview that points to 12 one-level-deep reference files, each with a clear one-line annotation under a well-signaled '## Reference Docs' section, and every referenced path resolves to an existing file in ./references/, matching 'Clear overview with well-signaled one-level-deep references; easy navigation'.

5 / 5

Total

19

/

20

Passed

Description

48%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 clearly scopes the skill to FigJam use of the use_figma MCP tool and distinguishes it from the foundational figma-use skill, but it is action-light and lacks an explicit 'Use when…' trigger clause with natural user phrases.

Suggestions

Add an explicit 'Use when…' trigger clause listing natural phrases a user would say, e.g. 'Use when creating or editing FigJam boards, stickies, connectors, sections, or tables'.

Enumerate 2-4 concrete actions instead of the generic 'use… in the FigJam context' (e.g. 'Create and arrange FigJam boards, stickies, connectors, sections, and tables').

Include natural synonyms and the board URL pattern as trigger terms ('FigJam board', 'figma.com/board', 'sticky notes').

DimensionReasoningScore

Specificity

The description names the domain ("use_figma MCP tool in the FigJam context") but the only action framing is the generic "use… in the FigJam context" with no enumerated concrete operations, matching the anchor 'Names the domain but actions are minimal or generic'; not a 3 because there is not even 1-2 specific actions listed.

2 / 5

Completeness

It has a clear 'what' (use Figma's use_figma MCP tool for FigJam) but no 'when'/Use-when clause with trigger phrases, so per the rubric a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords are present ("FigJam", "use_figma", "Figma") but it misses common natural phrases a user would say ("board", "sticky", "FigJam board"), placing it at 'Some relevant keywords but missing common variations'; not a 4 because keyword coverage is incomplete.

3 / 5

Distinctiveness Conflict Risk

It is explicitly scoped to FigJam and distinguishes itself from the sibling figma-use skill ('Can be used alongside figma-use which has foundational context'), giving a mostly-distinct niche with only minor overlap risk with that closely related skill.

4 / 5

Total

12

/

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

relative_links

Relative link issues: 4 suspicious

Warning

Total

15

/

16

Passed

Repository
figma/mcp-server-guide
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.