Security audit

Work Productivity Gog Google Workflow Helper

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-style workflow helper with overly broad auto-invocation triggers, but no hidden code, credential access, persistence, or destructive behavior was found.

This skill is reasonable to install if you want generic workflow guidance for Gog/Google Workspace inspired tasks. Be aware that it may activate on ordinary Google, Gmail, Drive, CLI, or bug-fix requests; prefer explicit invocation or disable implicit invocation if your environment supports that.

A.I.G

Vulnerability Patterns

Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (11)

Vague Triggers

High

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The manifest description uses very broad terms like work-productivity, google, workspace, cli, workflow, artifact, checklist, and analysis, which can cause the platform to invoke this skill for many unrelated user requests. Over-broad routing increases the chance that a user is steered into an unintended workflow, causing prompt-scope confusion, incorrect tool suggestions, or inappropriate handling of sensitive productivity data.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The trigger keywords include highly generic and high-frequency terms such as google, workspace, cli, gmail, calendar, drive, contacts, and bug fix without contextual constraints. In a skill-routing system, this can aggressively overmatch normal productivity requests and divert users into a skill that was not intended for their task, expanding exposure to sensitive enterprise context and degrading security boundaries between skills.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The trigger keywords are very broad and include common terms such as 'google', 'workspace', 'cli', 'gmail', 'calendar', and 'drive'. This can cause the skill to be invoked for many unrelated requests, leading to unintended routing, overbroad access to user workflows, and reduced trust in skill selection. In this context, the skill is positioned as a general helper across productivity tasks, which increases the chance of accidental activation rather than reducing it.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The trigger sentences are written as broad natural-language prompts that can match ordinary user requests rather than a narrowly scoped invocation pattern. This can cause unintended skill activation, leading the agent to apply this workflow in contexts where it was not explicitly requested, which increases the risk of irrelevant actions, confusion, or unsafe task routing.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The trigger examples are broad natural-language phrases that resemble ordinary user requests rather than narrowly scoped invocation patterns. This can cause unintended activation of the skill in unrelated conversations, which may route users into workflows involving Google/Workspace-style productivity actions when they did not explicitly request this specific helper.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The trigger phrases are generic enough to match ordinary productivity and Google Workspace requests, which can cause this skill to activate outside its intended scope. Over-broad invocation increases the chance of unintended routing, prompt interference with other skills, and users receiving actions or guidance from a workflow they did not explicitly request.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 91% confidence
Finding: The example trigger sentences rely on vague natural-language phrasing like 'Help me' and 'I need a practical workflow' and do not clarify boundaries for activation. This encourages accidental invocation from common user phrasing, which can misroute conversations and cause the agent to apply an irrelevant or overly broad workflow to potentially sensitive work-productivity tasks.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 90% confidence
Finding: The activation criteria in the description are vague, stating the skill should be used for broad categories like work-productivity, gog, google, workspace, and practical support needs. Ambiguous enablement conditions can make the orchestrator select this skill when a more appropriate or safer skill should handle the request, increasing accidental execution and context leakage across unrelated tasks.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The default prompt uses a very broad invocation phrase and generic capability wording, which increases the chance the skill will be activated in contexts the user did not specifically intend. This can cause prompt-routing mistakes, accidental tool/skill selection, and unintended disclosure or modification of work artifacts if the surrounding agent ecosystem auto-invokes skills based on loose matching.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 94% confidence
Finding: Enabling implicit invocation without clear trigger constraints allows the platform to auto-select this skill based on ambiguous user requests. In a productivity and workflow context, that raises the risk of unintended execution paths, cross-skill confusion, and the skill handling sensitive business content without sufficiently explicit user choice.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The keyword list includes very broad terms such as work-productivity, google, workspace, and cli, which are common across many unrelated requests. In a skill-routing system, such underspecified triggers can over-match and invoke this skill for tasks outside its intended scope, reducing reliability and potentially causing incorrect handling of user requests.
Content: No source excerpt is available for this finding.