What does this skill do, and when should you use it?
This skill creates a new blank Figma Design or FigJam file in the drafts folder for a selected plan. It accepts an editor type and file name, defaulting to design and Untitled when omitted. If no planKey is available, it calls whoami to resolve the available plans; users must choose when multiple plans are returned. It depends on the create_new_file MCP tool, and its source repository is marked deprecated.
Parses the optional editorType and fileName arguments; calls whoami when planKey is missing; calls create_new_file with planKey, fileName, and editorType; and returns file_key and file_url for later use with use_figma.
- A designer needs a fresh blank Figma file before starting design work.
- A product team needs a new FigJam board for collaborative planning.
- A user wants a named file created in the drafts folder of a selected plan.
- An agent needs a new file before making subsequent use_figma calls.
How do you install this skill?
- Creating a Figma file changes external state; confirm the target plan, file name, and editorType, and verify MCP availability before use.
- The repository is marked deprecated and the skill license is unknown; confirm the successor repository, licensing, and maintenance status before installation or distribution.
- No recovery or user-feedback procedure is specified for invalid input, permission failure, or network unavailability.
- MCP Server
create_new_file MCP toolwhoami tool
The skill is located at skills/.curated/figma-create-new-file/ in the repository. According to the README, run $skill-installer figma-create-new-file in Codex to install a curated skill, then restart Codex. The repository README does not provide this skill's individual license; it says to check LICENSE.txt in the skill directory.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/openai/skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/.curated/figma-create-new-file" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Invoke /figma-create-new-file [editorType] [fileName]. For example, /figma-create-new-file creates a design file named Untitled; /figma-create-new-file figjam My Whiteboard creates a FigJam file named My Whiteboard; and /figma-create-new-file design My New Design creates a design file named My New Design. If multiple plans are available and no planKey was supplied, select the target team or organization.
What are this skill's strengths and limitations?
- Supports both design and figjam editor types.
- Provides clear defaults for omitted arguments.
- Returns file_key and file_url for subsequent Figma operations.
- Defines planKey handling for both single-plan and multi-plan accounts.
- Requires the create_new_file MCP tool, but the source does not document how to configure or obtain it.
- Multiple-plan accounts require a user choice, so plan resolution is not always automatic.
- Creates only a blank file; it does not add design content or perform later editing.
- The source repository is deprecated, and the README recommends the OpenAI Plugins repository instead; no test information is provided.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Figma Blank File Creator this page ✓ OpenAI · Official | 53 · Use with care | ★ 28k | 4mo ago | — |
| Figma Design System Builder ✓ OpenAI · Official | 49 · Use with care | ★ 28k | 4mo ago | — |
| Figma Plugin API Operator ✓ OpenAI · Official | 47 · Use with care | ★ 28k | 4mo ago | — |
| Figma Design System Screen Builder ✓ OpenAI · Official | 46 · Use with care | ★ 28k | 4mo ago | — |
| Figma Code Connect Mapper ✓ OpenAI · Official | 54 · Use with care | ★ 28k | 4mo ago | — |
How did FollowSkills review this skill?
The skill limits creation to a blank Figma/FigJam file in the selected plan's drafts folder and requires user selection when multiple plans exist, providing some scoping and confirmation control. Points are deducted because file creation is an external state change without an explicit final confirmation step; data flow, sensitive-data handling, rollback/deletion, and dependency-security guidance are incomplete.
The workflow, defaults, call order, and returned fields are internally consistent. Points are deducted because failures from whoami, create_new_file, missing plans, invalid editorType/fileName, or unavailable MCP are not given diagnosable handling; this is a static review with no execution evidence, so the score is capped at 10.
Audience, invocation scenarios, parameters, defaults, and handoff to use_figma are reasonably clear, and supported editor types are stated. Points are deducted for missing non-fit cases, naming constraints, and trigger boundaries; Chinese-language interaction is not addressed, and mainland-China reachability of the external Figma MCP is unverified.
The documentation is readable and includes arguments, examples, workflow, dependency, and a maintainer entry. Points are deducted because the repository is marked deprecated, the individual skill license is unknown, and versioning, changelog, detailed maintenance ownership, update path, and troubleshooting guidance are absent.
The happy path is intended to return a file_key and file_url that can be used directly with use_figma, and the core task is narrowly defined. Points are deducted because no representative output or execution verification is provided and behavior for malformed inputs is unknown; static calibration caps effectiveness at 7.
The source files provide auditable workflow, parameter, and MCP dependency descriptions, allowing limited text-based verification. Points are deducted because there is no test suite, CI coverage, third-party execution evidence, or cross-source corroboration; static calibration caps verifiability at 5.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →