Work Productivity Gog Google Workflow Helper

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

Overview

This is a documentation-only workflow helper with broad activation language but no hidden commands, credential handling, persistence, or data exfiltration behavior.

Install only if you want a general workflow/planning helper for Gog-style Google Workspace tasks. Be aware it may activate on broad Google, workspace, CLI, or bug-fix phrasing, so invoke it explicitly for best control and review any generated workflow before applying it to real accounts or business data.

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

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: The trigger phrases are generic enough to match ordinary productivity and workflow requests, which can cause the skill to activate outside its intended scope. In an agent ecosystem, over-broad routing can misdirect user tasks, increase unintended access to related tooling or data domains, and make it easier for a loosely scoped skill to influence workflows it was not meant to handle.

Vague Triggers

High

• Confidence: 89% confidence
• Finding: The trigger phrases are broad enough to match common requests about Google, workspace, CLI, or productivity, which can cause the skill to activate outside its intended scope. Over-broad activation increases the chance of unintended invocation, prompt-routing mistakes, and accidental exposure of users to workflows or instructions not relevant to their request.

Vague Triggers

High

• Confidence: 97% confidence
• Finding: The skill description is broad enough to match many ordinary productivity or Google Workspace requests, which can cause the skill to activate outside its intended scope. Over-broad activation increases the chance that unrelated user tasks are routed through this skill, creating prompt-surface expansion and making downstream unsafe instructions or poor-fit automations more likely to influence behavior.

Vague Triggers

High

• Confidence: 98% confidence
• Finding: The keyword list includes highly ambiguous terms such as 'google', 'workspace', 'cli', and 'bug fix', which are common across many benign requests and unrelated domains. This makes accidental or excessive triggering likely, undermining least-privilege skill selection and allowing the skill to intercept conversations it was not designed to handle.

Vague Triggers

Medium

• Confidence: 94% confidence
• Finding: The example trigger phrases use everyday language like 'help me' and 'I need a practical workflow' without meaningful boundaries, reinforcing broad matching behavior. Examples often shape how systems and authors operationalize activation, so unconstrained examples can normalize triggering on vague user requests and increase unintended invocation frequency.

Vague Triggers

High

• Confidence: 97% confidence
• Finding: The trigger keyword list includes very generic terms such as 'google', 'workspace', and 'cli', which are common across many unrelated requests. This can cause unintended skill invocation, leading the agent to route users into this skill when it is not relevant and potentially exposing workflows, assumptions, or automated actions in the wrong context.

Vague Triggers

High

• Confidence: 94% confidence
• Finding: The manifest description says the skill should be used when a user asks for broad categories like work-productivity, google, workspace, or practical support artifacts, which spans a large amount of normal conversation. An overly broad activation description increases the chance of accidental invocation and misrouting, making downstream actions less predictable and less safe.

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: The example trigger phrases use very common conversational patterns like 'Help me' and 'I need a practical workflow', which resemble ordinary user speech rather than unique invocation examples. This makes false activations more likely, especially when combined with the already broad topic scope of the skill.

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: The skill enables implicit invocation with no documented trigger restrictions, so it may activate in broader contexts than intended. For a workflow/helper skill tied to Google Workspace and productivity tasks, ambiguous activation can cause the agent to inject guidance or actions into unrelated conversations, increasing the chance of unsafe tool use, prompt-scope confusion, or unintended data handling.

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: The trigger examples are overly broad and use common terms like 'google', 'workspace', and generic help phrasing, which can cause the skill to activate outside its intended scope. In an agent ecosystem, this can lead to misrouting user requests, unintended invocation on unrelated tasks, and increased exposure to downstream actions or data handling the user did not intend.

VirusTotal

64/64 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.