Install
$ agentstack add skill-ulises-jeremias-agent-toolkit-figma-create-new-file ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
createnewfile — Create a New Figma File
Use the create_new_file MCP tool to create a new blank Figma file in the user's drafts folder. This is typically used before use_figma when you need a fresh file to work with.
Skill Arguments
This skill accepts optional arguments: /figma-create-new-file [editorType] [fileName]
- editorType:
design(default) orfigjam - fileName: Name for the new file (defaults to "Untitled")
Examples:
/figma-create-new-file— creates a design file named "Untitled"/figma-create-new-file figjam My Whiteboard— creates a FigJam file named "My Whiteboard"/figma-create-new-file design My New Design— creates a design file named "My New Design"
Parse the arguments from the skill invocation. If editorType is not provided, default to "design". If fileName is not provided, default to "Untitled".
Workflow
Step 1: Resolve the planKey
The create_new_file tool requires a planKey parameter. Follow this decision tree:
- User already provided a planKey (e.g. from a previous
whoamicall or in their prompt) → use it directly, skip to Step 2.
- No planKey available → call the
whoamitool. The response contains aplansarray. Each plan has akey,name,seat, andtier.
- Single plan: use its
keyfield automatically. - Multiple plans: ask the user which team or organization they want to create the file in, then use the corresponding plan's
key.
Step 2: Call createnewfile
Call the create_new_file tool with:
| Parameter | Required | Description | |-------------|----------|-------------| | planKey | Yes | The plan key from Step 1 | | fileName | Yes | Name for the new file | | editorType| Yes | "design" or "figjam" |
Example:
{
"planKey": "team:123456",
"fileName": "My New Design",
"editorType": "design"
}
Step 3: Use the result
The tool returns:
file_key— the key of the newly created filefile_url— a direct URL to open the file in Figma
Use the file_key for subsequent tool calls like use_figma.
Important Notes
- The file is created in the user's drafts folder for the selected plan.
- Only
"design"and"figjam"editor types are supported. - If
use_figmais your next step, install and load the opt-infigma-use
pack first (see docs/SKILLS.md).
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ulises-jeremias
- Source: ulises-jeremias/agent-toolkit
- License: MIT
- Homepage: https://ulises-jeremias.github.io/agent-toolkit-archive/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.