Figma Sync
PassAudited by ClawScan on May 1, 2026.
Overview
Figma Sync appears purpose-aligned for syncing Figma designs and generated code, but it uses a Figma access token and stores design data locally, so users should handle it carefully.
Use this skill only with a Figma token you are comfortable granting to the target files. Review generated diffs and plugin specs before applying changes, and keep `.figma-cache/` plus generated outputs out of commits or shared folders.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Anyone using the skill is giving it Figma account/file access within the permissions of the token.
The skill requires a Figma personal access token even though the registry metadata lists no primary credential or required environment variable. This is expected for a Figma integration, but the token may grant access to private Figma files.
export FIGMA_TOKEN="your-personal-access-token"
Use a token with the least access needed, limit use to intended file keys, avoid sharing the token, and revoke it when no longer needed.
Private design structure, text, styles, or assets may remain on disk in the working directory.
Figma API responses are cached locally. This is disclosed and useful for rate limiting, but cached design data can persist after the task.
CACHE_DIR = Path(".figma-cache") ... cache_file.write_text(json.dumps(data, sort_keys=True))Keep `.figma-cache/` and generated output out of source control, use a trusted workspace, and delete cached files when they are no longer needed.
If a user applies a generated patch through the companion plugin/spec workflow, it could change shared Figma designs.
The skill documents a write/apply workflow for Figma changes. The artifacts also state dry-run is the default and the code indicates node mutations require a companion plugin, so this is purpose-aligned but high-impact if applied.
python3 scripts/figma_push.py --file-key <KEY> --patch-spec patch.json --execute # actually apply Dry-run by default. Pass `--execute` to apply changes.
Run preview/diff first, inspect `patchSpec.json` and `pluginSpec.json`, and only apply changes after confirming the target file and operations.
Users have less external provenance information and may need to satisfy undeclared local Python dependencies themselves.
The artifacts include local Python scripts but no provenance homepage or install/dependency declaration. No hidden remote installer is shown, so this is a review note rather than a concern.
Source: unknown Homepage: none No install spec — this is an instruction-only skill.
Review the included scripts before use, run them in a project workspace you trust, and ensure dependencies such as Python and `requests` come from trusted sources.