Work Productivity Gog Google Workflow Helper

• Outcome: Pass
• Latest audit: Jul 29, 2026 · 7:42 AM UTC
• Version: 0.20260729.110214

Overview

This is a documentation-only workflow helper with overly broad activation wording but no hidden execution, persistence, credential use, or destructive behavior.

Before installing, be aware that the skill may activate on broad Google Workspace or productivity wording. It appears safe as guidance material, but users should confirm they intended to use this skill before applying any generated workflow to Gmail, Calendar, Drive, or CLI tasks.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (9)

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: The trigger phrases are generic help-seeking sentences that can match ordinary user requests unrelated to this specific skill. That increases the chance of unintended invocation, causing the agent to route users into this workflow when they did not ask for it, which can lead to confusing actions, over-privileged task selection, or unexpected handling of Google Workspace-related requests.

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: The trigger phrases are broad enough to match ordinary productivity or workflow requests, which can cause the skill to activate outside its intended scope. In an agent ecosystem, over-broad invocation increases the chance of unintended tool use, irrelevant workflow execution, or accidental handling of sensitive Google Workspace-related tasks when the user did not explicitly request this skill.

Vague Triggers

High

• Confidence: 97% confidence
• Finding: The description uses very broad terms like "google," "workspace," "cli," "practical workflow," and "implementation support," which can cause the skill to activate for many unrelated requests. Overbroad routing increases the chance of mis-invocation, causing the wrong skill to handle sensitive user tasks and potentially produce unsafe or irrelevant actions under an incorrect context.

Vague Triggers

High

• Confidence: 98% confidence
• Finding: The trigger keywords include highly generic terms such as "google," "workspace," "cli," "gmail," "calendar," and "drive," which are common across many ordinary requests. This makes accidental invocation likely, and in an agent setting that can redirect user intent to an overly powerful or mismatched workflow, increasing the chance of incorrect automation, data handling mistakes, or policy bypass through bad routing.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The example trigger sentences are vague, repetitive, and malformed, so they do not provide reliable guidance for safe invocation. Poor examples train routing behavior toward ambiguous matches, which can amplify accidental activation and make it harder for maintainers or agents to distinguish legitimate use from unrelated requests.

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: The trigger list includes broad, common terms such as "google", "workspace", and "cli", which can match many unrelated user requests and cause the skill to activate unexpectedly. Over-broad activation increases the chance that the agent applies this skill in the wrong context, leading to irrelevant guidance, unsafe assumptions, or unintended handling of adjacent tasks.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The description says to use the skill when a user asks for broad categories like work-productivity, gog, google, workspace, or cli, which leaves the invocation boundary poorly defined. This ambiguity can cause accidental routing of unrelated requests into this skill, reducing reliability and potentially introducing inappropriate instructions or data handling in contexts the skill was not designed for.

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: The default prompt trigger phrase is extremely broad and includes common productivity and workflow terms, which increases the chance of accidental or implicit invocation during normal user conversations. Because implicit invocation is enabled, this can cause the skill to activate outside clear user intent, potentially exposing users to unintended actions, prompt steering, or expanded access to workflow logic.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger examples are broad, natural-language phrases that can match ordinary user requests unrelated to this skill, increasing the chance of unintended activation. In an agent ecosystem, over-broad routing can cause the wrong skill to handle sensitive workflow, Google Workspace, or CLI-related requests, leading to inappropriate actions, confusing outputs, or exposure of context to a skill that was not explicitly intended.

VirusTotal

64/64 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.