figma-code-connect
Pass
Audited by Gen Agent Trust Hub on Sep 9, 2026
Risk Level: SAFEINDIRECT_PROMPT_INJECTIONEXTERNAL_DOWNLOADSDYNAMIC_EXECUTION
Full Analysis
- [INDIRECT_PROMPT_INJECTION]: The skill processes component data from Figma nodes which could potentially contain malicious instructions intended to influence the generated code or the agent's workflow.
- Ingestion points: Figma node metadata, component names, and property definitions are retrieved through the
get_context_for_code_connectandget_code_connect_suggestionstools. - Boundary markers: The skill does not explicitly use specific delimiters to isolate Figma-provided data within the generated templates.
- Capability inventory: The skill can search the local codebase for components, write new
.figma.tsfiles, and prompt the execution of CLI commands likenpx figma connect publish. - Sanitization: While the skill uses
figma.codetagged templates for formatting the output, it does not explicitly validate or sanitize the raw string values retrieved from Figma properties before interpolation. - [DYNAMIC_EXECUTION]: The core functionality of the skill involves generating executable template files based on external metadata.
- Evidence: Instructions in
SKILL.mdand thereferences/directory guide the creation of.figma.tsand.figma.jsfiles that utilize thefigmaAPI. - Context: These scripts are generated from design metadata and are intended for processing by the official Figma Code Connect CLI utility.
- [EXTERNAL_DOWNLOADS]: The skill references external tools and repositories necessary for the Code Connect workflow.
- Evidence: The documentation recommends installing the
@figma/code-connectpackage from the NPM registry and references the official Figma MCP server guide on GitHub. - Trust: These resources originate from the
figmaorganization, which is a recognized and well-known service provider.
Audit Metadata