Work Productivity Gog Google Workflow Helper

• Outcome: Pass
• Latest audit: Jul 29, 2026 · 6:51 AM UTC
• Version: 0.20260729.110214

Overview

This is a documentation-only workflow helper with broad activation wording but no evidence of credential access, persistence, exfiltration, or destructive behavior.

This skill appears safe to install as a general workflow helper, but users should be aware it may be invoked for loosely related Google, Workspace, CLI, or bug-fix requests. Review whether its broad trigger terms fit your environment, especially if you use many skills with overlapping productivity or Google Workspace scopes.

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 (11)

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The trigger examples are broad, generic phrases that can match ordinary user requests about workflows, bug fixes, or setup help, causing the skill to activate outside its intended niche. In an agent ecosystem, this can lead to skill hijacking or unintended routing where the agent applies this workflow in contexts the user did not explicitly choose, increasing the chance of irrelevant actions or unsafe delegation.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The README defines a wide keyword and trigger scope without clear boundaries, exclusions, or prerequisites, making it ambiguous when the skill should be selected. Because the skill covers broad terms like work-productivity, google, workspace, and cli, it can overshadow other more appropriate skills and cause misrouting in multi-skill environments.

Vague Triggers

Medium

• Confidence: 94% confidence
• Finding: The trigger phrases are broad enough to match common requests about productivity, Google Workspace, CLI, or bug fixing, which can cause the skill to activate outside its intended scope. In an agent ecosystem, over-broad routing can expose users to unintended instructions, create confusing task selection, and increase the chance that a less appropriate skill handles sensitive workflow requests.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The skill description uses very broad activation terms like "google," "workspace," "cli," "analysis," and "implementation support," which can match many unrelated requests and cause unintended invocation. In an agent environment, over-broad routing can expose irrelevant instructions, create prompt-selection confusion, and increase the chance this skill handles requests outside its intended scope.

Vague Triggers

High

• Confidence: 97% confidence
• Finding: The trigger keywords include highly ambiguous everyday terms such as "google," "workspace," "cli," and "bug fix," which are likely to collide with ordinary user language. This makes accidental invocation much more likely, and in multi-skill systems that can lead to misrouting, inappropriate tool/workflow suggestions, or interference with more suitable skills.

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: The example trigger sentences are generic and repetitive, and they do not define clear invocation boundaries or provide negative examples. Without examples showing when the skill should not activate, integrators and routing systems may overgeneralize and invoke it for loosely related productivity or Google-related requests.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger list includes very broad everyday terms such as "google", "workspace", and "cli", which can cause the skill to activate for many unrelated requests. Over-broad activation increases the chance of accidental routing, exposing users to irrelevant instructions or causing this skill to override a more appropriate and safer skill.

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: The description says to use the skill when a user asks about broad categories like work-productivity, gog, google, workspace, or cli, but it does not define precise boundaries for applicability. This ambiguity can lead orchestration systems or users to invoke the skill outside its intended scope, reducing reliability and potentially surfacing unsafe or incorrect workflow guidance in unrelated contexts.

Vague Triggers

Medium

• Confidence: 96% confidence
• Finding: The default prompt contains broad, everyday phrasing such as "help me" and general workflow-related language that can match many unrelated user requests, increasing the chance of unintended or implicit invocation. Because the policy also enables implicit invocation, this skill may activate in contexts the user did not clearly intend, causing prompt-scope expansion, confusion, or unreviewed execution paths.

Vague Triggers

High

• Confidence: 93% confidence
• Finding: The trigger sentence is phrased so broadly that ordinary user requests containing common productivity language could activate this skill unintentionally. In an agent-routing context, overbroad activation can cause the wrong skill to run, leading to prompt-scope confusion, irrelevant access to Google/Workspace-oriented workflows, and increased exposure to downstream unsafe actions if the skill later handles sensitive operations.

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: This trigger is ambiguous about when the skill should activate and does not clearly bound the scope to specific Google/Gog workflow tasks. Ambiguous routing criteria can cause accidental invocation on unrelated requests, which is especially risky for a skill associated with workspace, CLI, Gmail, Calendar, Drive, and contacts workflows because misrouting may expose users to inappropriate automation suggestions or unintended task handling.

VirusTotal

64/64 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.