Work Productivity Gog Google Workflow Helper

• Outcome: Pass
• Latest audit: Sep 16, 2026 · 9:46 AM UTC
• Version: 0.1.1

Overview

This is a documentation-only workflow helper with overly broad activation wording, but it does not contain code, credential handling, persistence, or hidden actions.

Before installing, consider narrowing or explicitly invoking this skill because its keywords include broad terms like Google, workspace, CLI, Gmail, Calendar, Drive, Contacts, and bug fix. The artifact itself is low risk, but broad implicit activation could make it appear during unrelated productivity tasks.

A.I.G

Vulnerability Patterns

• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally
• Unauthorized Access and Privilege Escalation: Obtains permissions beyond the task's legitimate needs

SkillSpector

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

Vague Triggers

High

• Category: Not specified by scanner
• Confidence: 97% confidence

Finding

The skill description and activation guidance are broad enough to match many ordinary productivity or Google Workspace requests, which can cause the wrong skill to be invoked. Over-broad invocation is dangerous because it can route users into irrelevant workflows, create unintended authority for this skill, and increase the chance that future unsafe instructions in the skill are applied outside their intended scope.

Content

No source excerpt is available for this finding.

Vague Triggers

High

• Category: Not specified by scanner
• Confidence: 98% confidence

Finding

The keyword list uses highly ambiguous terms such as 'google', 'workspace', 'cli', 'gmail', 'calendar', and 'bug fix' without qualifiers, making accidental or excessive triggering likely. In an agent ecosystem, this can lead to skill hijacking of unrelated requests, reducing routing integrity and potentially exposing users to inappropriate instructions or actions under the wrong workflow context.

Content

No source excerpt is available for this finding.

Vague Triggers

High

• Category: Not specified by scanner
• Confidence: 96% confidence

Finding

The trigger keywords are overly broad, including generic terms like "google", "workspace", "cli", and common product names such as Gmail/Calendar/Drive. This can cause the skill to activate in many unrelated contexts, leading to inappropriate instruction injection into user workflows, confusion, or accidental handling of requests outside the skill’s intended scope.

Content

No source excerpt is available for this finding.

Vague Triggers

High

• Category: Not specified by scanner
• Confidence: 98% confidence

Finding

The trigger sentence is overly broad and can match ordinary user language, causing the skill to activate in contexts the user did not explicitly intend. That increases the chance of incorrect routing, prompt-surface expansion, and accidental execution of workflow logic for unrelated requests, which is a real security and reliability concern for agent systems.

Content

No source excerpt is available for this finding.

Vague Triggers

High

• Category: Not specified by scanner
• Confidence: 96% confidence

Finding

This generic request pattern lacks scope constraints and could cause the skill to be selected for a wide range of loosely related productivity requests. In an agent environment, such overmatching can misroute tasks, expose unrelated context to the skill, and undermine user intent verification, especially because the skill claims applicability across several broad domains.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

• Category: Not specified by scanner
• Confidence: 94% confidence

Finding

The trigger examples are phrased as broad, ordinary help requests rather than narrowly scoped activation cues, which can cause the skill to activate in contexts the user did not intend. In an agent ecosystem, this increases the risk of prompt-routing confusion, accidental invocation, and inappropriate handling of unrelated Google Workspace or productivity tasks, especially given the very generic keywords listed alongside the triggers.

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 broad, generic, and overlap with ordinary user requests such as asking for help with workflows, bug fixes, or Google Workspace tasks. This can cause the skill to activate in situations beyond its intended scope, increasing the chance of inappropriate tool use, unintended prompt interception, or the skill influencing unrelated tasks without clear user intent.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

• Category: Not specified by scanner
• Confidence: 93% confidence

Finding

The example triggers are built around generic language like 'Help me' and 'I need a practical workflow,' which teaches broad activation behavior instead of precise intent matching. This increases accidental invocation and weakens the dispatcher's ability to distinguish this skill from other general productivity helpers, especially given the already broad domain terms.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

• Category: Not specified by scanner
• Confidence: 91% confidence

Finding

The description says to use the skill when users ask for broad categories like work-productivity, gog, google, workspace, or cli, or when they need practical workflow/checklist/analysis support. This activation boundary is vague enough that the skill may be selected for many unrelated requests, increasing the risk of misrouting, policy bypass through wrong-tool invocation, or low-quality automated actions in the wrong context.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

• Category: Not specified by scanner
• Confidence: 77% confidence

Finding

该文件主体为中文，但关键需求描述、用户群体说明和触发示例中大量保留英文表达，如 L11、L13 及 L48-L50，且未说明应按用户语言偏好输出或允许语言切换。这可能造成语言策略不清晰，构成未提供用户语言选择的自然语言政策问题。

Content

No source excerpt is available for this finding.

Vague Triggers

Medium

• Category: Not specified by scanner
• Confidence: 95% confidence

Finding

The manifest enables implicit invocation while describing activation in very broad terms such as work productivity, Google, workspace, CLI, workflow, checklist, analysis, and implementation support. This can cause the skill to be auto-selected in many loosely related contexts, increasing the chance of unintended execution, overbroad data exposure to the skill, or user confusion about why this skill was invoked.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

• Category: Not specified by scanner
• Confidence: 76% confidence

Finding

Natural-language policy checks apply to all file types. This Chinese README contains substantial English instructional content and trigger phrases, but it does not state whether English is required, optional, or user-selectable, which can amount to an implicit language constraint without opt-in.

Content

No source excerpt is available for this finding.