figma-to-content

SUSPICIOUS. The core purpose and most capabilities are coherent for a Figma-to-Adobe content publishing skill, and data primarily flows to official Adobe endpoints. The main concerns are transitive trust in multiple orchestrated skills, acceptance of arbitrary remote Figma MCP implementations, limited credential-file access, and the ability to perform code pushes and optional live publication; these are significant but not fundamentally incompatible with the stated purpose.