Back to skill

Security audit

Game Design Roadblock Reframing

Security checks for vulnerabilities and agentic risk

Overview

This is a low-risk game design facilitation skill that only provides a structured thinking workflow and does not request system, file, network, credential, or persistence access.

This skill appears safe to install for game design problem-solving. Be aware that its trigger wording may cause it to be used in general discussions about a single blocker, so users who want tighter activation should narrow the description, but there is no evidence of hidden or high-impact behavior.

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

Low
Category
Not specified by scanner
Confidence
90% confidence
Finding

The invocation guidance says to use the skill when 'a team is stuck on one obstacle,' when discussion 'keeps collapsing into' a phrase, or when a plan 'feels trapped,' which are broad conversational conditions rather than narrowly scoped triggers. Because this is a markdown skill file and no explicit exclusion conditions or negative examples are provided, the trigger scope is somewhat ambiguous and may overlap with common design discussions.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.