figma-automation

This skill manifest is coherent with its stated purpose (automating Figma via a Composio/Rube MCP toolkit). The primary security concern is that it routes discovery, authentication, and all Figma API calls through a third-party MCP endpoint (https://rube.app/mcp). That design creates a single transitive trust boundary: the MCP can observe or mediate credentials, change tool schemas at runtime, and perform reads/writes on behalf of the user. There is no executable malware or obfuscated payload in the provided content. However, because OAuth flows and tool behavior are mediated remotely and dynamic, this poses a medium supply-chain risk unless the operator explicitly trusts the MCP provider, audits scopes returned during auth, and requires per-action confirmation for write operations. Recommend treating this as suspicious until Rube/Composio's security, token handling, and manifest integrity are independently verified.