Security audit
Security checks for vulnerabilities and agentic risk
This is a simple stereoscopic 3D feature-request helper with no executable code, persistence, or credential access.
Before installing, consider narrowing the trigger keywords or relying on explicit invocation so unrelated support or overview requests do not accidentally use this helper.
The trigger list includes very broad terms such as 'support', 'overview', 'mode', 'would', 'great', and 'maybe', which are common in ordinary conversation and unrelated requests. This can cause the skill to activate outside its intended stereoscopic-3D context, leading to incorrect routing, prompt-scope confusion, or unintended influence over benign user interactions.
The keyword list includes vague terms like 'support', 'overview', 'mode', 'would', 'great', and 'maybe', which are common in normal conversation and unrelated contexts. Such broad activation criteria can cause accidental invocation of the skill, reducing routing reliability and creating opportunities for inappropriate handling of user requests.
The trigger sentence is highly generic and can match ordinary user requests rather than a deliberate request to invoke this specific skill. That increases the chance of unintended activation, causing the agent to route unrelated conversations into this workflow and potentially produce irrelevant or misleading operational guidance.
The keyword list contains several broad or generic terms such as 'support', 'overview', 'mode', 'would', 'great', and 'maybe', which make invocation ambiguous. In a skill-routing system, these terms can match many unrelated conversations, causing accidental invocation and reducing reliability of task isolation.
The trigger phrase examples are overly generic help-seeking requests and can cause the skill to activate outside its intended domain. This increases the chance of unintended routing, where unrelated user requests are handled by this skill and receive irrelevant or misleading workflow guidance.
The description says to use the skill for 'business-and-operations, stereoscopic, support, overview, mode' and for broad needs like 'practical workflow, artifact, checklist, analysis, or implementation support,' but it does not clearly bound the subject matter to stereoscopic-3D requests. This ambiguity increases the chance of overbroad invocation and accidental application to unrelated tasks.
The example trigger 'Help me stereoscopic 3d support.' is a highly generic help-style phrase that resembles normal user language and could encourage loose matching behavior. In combination with the broad keyword list, it increases the likelihood of false activations rather than targeted use.
The skill description defines activation conditions broadly across vague business-and-operations and support-oriented requests without clear boundaries or exclusions. In an agent environment, ambiguous routing criteria increase the chance that this skill is selected for unrelated tasks, which can degrade task isolation and cause users to receive inappropriate guidance or generated modifications outside the intended stereoscopic 3D scope.
The trigger keyword list includes very broad, everyday terms such as "support", "overview", "mode", "would", "great", and "maybe". This can cause the skill to activate in unrelated conversations, leading to prompt-routing errors, irrelevant workflow generation, and unintended exposure of the skill’s instructions or outputs in contexts where it was not requested.
The default prompt and skill framing use broad, repetitive language around 'stereoscopic 3d support' without clear invocation boundaries, while implicit invocation is enabled. This can cause the agent to select the skill for loosely related requests, leading to unintended routing, user confusion, or inappropriate operational guidance in contexts that did not explicitly request this helper.
The trigger keyword "would" is extremely broad and likely to appear in many unrelated user requests, which can cause this skill to activate unintentionally. Over-broad invocation increases the chance of routing users into an irrelevant workflow, causing confusion, degraded reliability, and possible interference with more appropriate skills.
No suspicious patterns detected.
