Codex Figma skill feedback: put capability and scope first in the description
Hello Figma Support,
Please route this maintenance suggestion to the team responsible for the Figma plugin skills distributed for Codex. This concerns instruction discovery and packaging, rather than a Figma document or a demonstrated Plugin API failure.
Environment: Codex desktop on macOS. Installed component: figma@openai-curated-remote, version 2.0.21. Observation date: 2026-09-14.
In skills/figma-use/SKILL.md, the description at line 3 begins with mandatory prerequisite warnings and puts the actual capability and triggering objects later. In a display with limited description space, the warning is more likely to remain visible than the scope. The installed entry point has 34,998 characters and 435 lines. This is a static discovery concern, not a measured automatic-selection failure rate.
Suggested English description:
“Create, edit, or inspect nodes, components, variables, and layouts in Figma files using use_figma JavaScript. Read this skill’s API and execution requirements before calling the tool.”
Keep the required API conventions, file context, valid node sources, skillNames reporting, and actual runtime limitations. Route full Design, FigJam, Slides, and Motion procedures according to the task. Ordinary local webpage styling should not activate Figma solely because generic design terms are present.
Suggested acceptance cases:
- Update a known Figma node using the relevant API requirements.
- Create a full screen or component library with the needed workflow guidance.
- Use the appropriate file-type APIs for FigJam and Slides.
- Keep an unrelated local webpage edit in its chosen environment.
Public source reference: https://github.com/openai/plugins/blob/1dc195897af4161d039b80d8471ec0a10c9bbc89/plugins/figma/skills/figma-use/SKILL.md#L3
The public manifest at this revision reports 2.0.20, while the installed version is 2.0.21; these are not being treated as identical package releases. The public repository currently disables Issues and Discussions and limits PR creation to collaborators, so we are using the official support route.
We have not modified the installed plugin or verified a fixed release. Please advise whether your team maintains this skill text or can direct this feedback to the responsible team.