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.
54
61%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/figma-use-figjam/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too vague and meta-level, describing itself as helping use a tool rather than explaining what concrete tasks it enables. It lacks specific actions, natural trigger terms users would say, and an explicit 'Use when...' clause. The reference to a companion skill ('figma-use') adds some context but also introduces ambiguity about scope boundaries.
Suggestions
Add specific concrete actions the skill enables, e.g., 'Creates and organizes sticky notes, draws connectors, manages sections, and arranges content on FigJam boards.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user wants to create or edit FigJam boards, whiteboards, brainstorming sessions, sticky notes, or collaborative diagrams.'
Clarify the boundary with the companion 'figma-use' skill by stating what this skill handles that the other does not, e.g., 'Extends figma-use with FigJam-specific widget types and layout patterns.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description does not list any concrete actions. It says 'helps agents use Figma's use_figma MCP tool in the FigJam context' which is vague about what specific capabilities or actions are performed (e.g., creating sticky notes, drawing connectors, organizing boards). | 1 / 3 |
Completeness | The 'what' is extremely vague ('helps agents use... MCP tool') and there is no explicit 'when' clause. The description lacks any 'Use when...' guidance, and the what portion doesn't describe concrete functionality, so both dimensions are weak. | 1 / 3 |
Trigger Term Quality | It includes some relevant keywords like 'Figma', 'FigJam', 'use_figma', and 'MCP tool', but these are mostly technical/tool-specific terms. It misses natural user terms like 'whiteboard', 'sticky notes', 'brainstorming', 'diagram', or 'collaboration board'. | 2 / 3 |
Distinctiveness Conflict Risk | It distinguishes itself from the general 'figma-use' skill by specifying the FigJam context, which provides some differentiation. However, the boundary between this skill and the foundational 'figma-use' skill is unclear, creating potential overlap and confusion about when to use one versus the other. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exceptionally well-crafted skill file. It is concise yet comprehensive, providing FigJam-specific constraints, gotchas, and workflows without over-explaining concepts Claude already knows. The progressive disclosure is excellent with clearly organized references, and the actionability is high with specific tool names, parameters, error messages, and concrete code examples. The workflow guidance includes proper sequencing and error recovery patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section delivers information Claude wouldn't already know — FigJam-specific gotchas, tool constraints, canonical recipes, and critical warnings. No unnecessary explanations of basic concepts. | 3 / 3 |
Actionability | Provides concrete, actionable guidance throughout: specific tool names and parameters (`skillNames: "figma-use-figjam"`), exact error messages to expect, a concrete ToolSearch batch syntax example, and clear do/don't instructions (e.g., don't use `figma.createImage()`, use `upload_assets` instead). | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation checkpoints: inspect with `get_figjam` first, then reference IDs in `use_figma`; load font → await → mutate → return for text mutations; load schemas in batch before calling tools. Error recovery is addressed (e.g., if you forgot to return an ID, call `get_figjam` again). | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview in the main file and 12+ clearly labeled, well-signaled one-level-deep references. Each reference link includes a brief description of what it covers, making navigation easy. Cross-references to the parent figma-use skill are also clearly signaled. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- figma/mcp-server-guide
- Commit
a742f0a
- 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.