Back to skill

Security audit

Figma Annotation Guide

Security checks for vulnerabilities and agentic risk

Overview

This skill is a plain Markdown guide for creating Figma developer handoff annotations and does not request system access, credentials, persistence, or code execution.

Before installing, consider whether the broad trigger wording could make the skill activate for general design-documentation requests. Its behavior is otherwise transparent and limited to producing annotation guidance.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The trigger phrase "Document this design for the engineering team" is broad and could match many ordinary requests about design communication, not just this specific Figma annotation workflow. The file provides example triggers but no exclusion conditions or scope limits to distinguish when this skill should activate versus other documentation or design-review skills.

Content

No source excerpt is available for this finding.