Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation-only workflow helper with overly broad activation wording but no code, credential handling, persistence, or hidden high-impact behavior.
Install only if you want a general Gog-style Google Workspace workflow-planning helper. Be aware it may activate on broad Google or productivity prompts, so prefer explicit invocation and review its advice before using it for real workspace changes.
The skill description and activation scope are broad enough to match many ordinary productivity or Google-related requests that may not actually need this specialized skill. Over-broad routing can cause the wrong skill to be invoked, leading to confused delegation, reduced reliability, and accidental exposure of user context to an irrelevant workflow.
The trigger sentences are written as broad natural-language requests that overlap with common user phrasing, which can cause the skill to activate when the user did not explicitly intend to invoke it. In an agent ecosystem, unintended invocation can route tasks into the wrong workflow, leading to incorrect actions, confusion, or unnecessary access to Google Workspace-related contexts.
The trigger sentences and keywords are broad enough to match many ordinary productivity or Google Workspace requests, causing the skill to activate outside its intended scope. Over-broad activation can route unrelated user tasks into this skill, increasing the chance of inappropriate instructions, user confusion, or unintended access patterns if the skill later handles sensitive workflow actions.
The trigger phrases are broad enough to match ordinary requests involving Google Workspace, CLI, or general productivity help, which can cause the skill to activate outside its intended scope. In an agent ecosystem, over-broad activation can route unrelated user tasks into this skill, increasing the chance of unintended actions, misleading workflow guidance, or privilege use under the wrong context.
The keyword list contains highly generic terms such as 'google', 'workspace', 'cli', 'gmail', 'calendar', and 'drive', which are common across many unrelated tasks. This increases the chance of false-positive triggering and misrouting, especially in environments where skills are auto-selected from sparse user prompts.
The example trigger phrases use extremely common lead-ins like 'Help me' and 'I need a practical workflow', which do not establish clear trigger boundaries. In systems that learn or infer routing behavior from examples, this can broaden activation beyond the intended domain and degrade safety and precision.
The skill description says to use the skill when users mention broad categories or need generic artifacts like workflows, checklists, analysis, or implementation support, but it does not clearly define exclusion conditions or boundaries. This ambiguity can cause accidental invocation on many unrelated productivity or Google-related tasks, increasing the chance of misrouting, confusion, or inappropriate guidance.
The trigger keywords are overly broad and include generic terms such as 'google', 'workspace', 'cli', and common product names, which can cause the skill to activate for unrelated user requests. This creates routing ambiguity and may lead the agent to apply irrelevant workflow instructions in contexts the user did not intend, reducing reliability and potentially interfering with safer or more appropriate skills.
The default prompt uses a very broad invocation phrase tied to common terms like work productivity, Google, workflow, and practical help, which can match ordinary user requests without clear boundaries. This increases the chance of unintended skill activation, causing the agent to inject this skill's instructions or behavior in contexts where the user did not explicitly request it.
Enabling implicit invocation without a specific trigger list or exclusion rules allows the platform to auto-select this skill in a wide range of ambiguous requests. In a broadly scoped productivity skill, that can lead to overbroad interception of user tasks, prompt-context contamination, and unintended execution paths that reduce predictability and safety.
In this Chinese README, key user-facing usage content and trigger phrases are written in English, which can impose a language expectation without explicitly offering localization choice. The file does not state that English is required or provide an opt-in/alternative for users who expect a fully Chinese experience.
