Work Productivity Gog Google Workflow Helper

• Outcome: Pass
• Latest audit: Jul 24, 2026 · 5:53 PM UTC
• Version: 0.1.0

Overview

This is a documentation-style workflow helper with broad activation wording, but it does not install code, access accounts, or perform actions by itself.

Before installing, understand that this skill may be invoked for broad Google, Workspace, Gmail, Calendar, Drive, or CLI-related requests. Review whether you want that routing behavior; otherwise its artifacts are advisory and should still require normal user approval before any real account or workspace changes are made.

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 sentences are broad enough to activate on generic productivity, Google, or workflow-related requests that may not actually require this skill. Over-broad activation can cause unintended routing, making the agent apply the wrong instructions or expose users to unexpected behavior in contexts involving Gmail, Calendar, Drive, or other sensitive workspace operations.

Vague Triggers

High

• Confidence: 92% confidence
• Finding: The trigger phrases are broad enough to match ordinary user requests such as asking for practical help with Google Workspace, CLI, or productivity tasks, which can cause the skill to activate outside its intended scope. In an agent ecosystem, overbroad routing can expose users to unintended instructions, increase prompt-surface area, and cause the wrong skill to handle sensitive workflow requests.

Vague Triggers

High

• Confidence: 94% confidence
• Finding: The skill description is extremely broad and includes generic terms like 'google', 'workspace', 'cli', and 'analysis', which can cause the skill to be invoked for many unrelated requests. Over-broad activation increases the chance that this skill intercepts tasks outside its intended scope, leading to misrouting, unintended execution paths, or inappropriate handling of sensitive productivity workflows.

Vague Triggers

High

• Confidence: 97% confidence
• Finding: The trigger list contains highly generic keywords such as 'google', 'workspace', 'cli', 'gmail', 'calendar', and 'drive' without contextual constraints. This makes accidental invocation likely across a wide range of unrelated or sensitive tasks, which is especially risky because the skill is positioned to produce workflows, automation, and implementation support that could influence user actions in security-relevant productivity environments.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger keywords are extremely broad, including common terms like 'google', 'workspace', 'cli', 'gmail', and 'calendar'. This can cause the skill to activate for ordinary requests outside its intended scope, leading to incorrect routing, unexpected prompt/context injection, and reduced trust in agent behavior.

Vague Triggers

High

• Confidence: 97% confidence
• Finding: The invocation description says to use the skill whenever a user mentions broad categories like work-productivity, google, workspace, cli, or asks for almost any practical workflow or analysis. This ambiguity makes over-selection likely, so the skill may intercept unrelated requests and influence outputs in contexts where it was not intended.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The example trigger phrases use generic everyday language such as 'Help me' and 'I need a practical workflow' with minimal constraints. These examples train broad matching behavior and increase accidental invocation risk, especially in systems that use examples as routing signals.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The skill enables implicit invocation but defines no trigger phrases, boundaries, or scope constraints, which can cause it to activate in unintended contexts. Because this skill is broadly framed around productivity, workflows, implementation help, and safety hardening, accidental routing could expose users to overly broad actions or instructions when they did not explicitly request this skill.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger phrases are broad, natural-language patterns that can match ordinary user requests rather than clear, intentional invocation of this specific skill. That can cause the wrong skill to activate in unrelated contexts, leading to unintended access to workflows, actions, or advice and increasing the attack surface for prompt-routing abuse or accidental execution.

VirusTotal

63/63 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.