Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation-only workflow helper with no executable payload, credentials, persistence, or hidden data handling, though its activation wording is overly broad.
Before installing, be aware that this skill may activate for ordinary Google, Workspace, CLI, or bug-fix requests because its triggers are broad. It appears low-risk, but users should confirm it is the intended workflow helper when it appears in unrelated productivity tasks.
The skill description is broad enough to match many ordinary productivity or Google Workspace requests that are not specifically about this workflow. Overbroad routing can cause unintended invocation, exposing users to irrelevant instructions, confusing behavior, and increased attack surface if a loosely related skill is selected in place of a more appropriate one.
The keyword list includes very common, high-collision terms such as 'google', 'workspace', 'cli', and 'bug fix', which are likely to appear in unrelated user requests. This substantially increases misrouting risk, making the skill eligible for many contexts beyond its intended scope and potentially interfering with safer or more specialized skills.
The trigger list includes very broad, high-frequency terms such as "google", "workspace", and "cli", which can cause this skill to activate for many unrelated requests. That increases the chance of unintended routing, confusing users, and causing the agent to apply the wrong workflow or expose unrelated capabilities in contexts where they were not requested.
The trigger examples are broad, natural-language phrases that can plausibly appear in ordinary user requests, increasing the chance that this skill is invoked when the user did not explicitly intend to use it. In an agent ecosystem, over-broad activation can route sensitive or unrelated tasks into the wrong workflow, causing inappropriate tool use, confusing outputs, or accidental data handling beyond user expectations.
The trigger phrases are extremely broad and partially mirror generic user requests, which can cause the skill to activate in contexts where it was not explicitly intended. In an agent ecosystem, ambiguous activation increases the risk of misrouting tasks, invoking the wrong workflow, or handling sensitive Google Workspace-related requests without sufficient user intent confirmation.
The trigger phrases are written as generic help requests that overlap with ordinary user language, which can cause the skill to activate unintentionally when a user is asking for broad workflow or bug-fix assistance. In an agent ecosystem, accidental invocation can route tasks into the wrong skill, leading to inappropriate actions, confused execution, or unintended access to Google Workspace-related workflows.
The example trigger phrases use generic everyday wording and repeat broad requirement text without clearly stating activation limits. This encourages ambiguous matching behavior and reinforces over-selection of the skill for requests that only loosely resemble the intended use case.
The invocation guidance uses open-ended conditions like using the skill whenever a user asks about broad categories or needs practical support, without defining exclusions or decision criteria. This ambiguity can lead to over-invocation, overlap with unrelated skills, and inconsistent agent behavior, especially because the described domain spans productivity, Google tools, CLI, artifacts, analysis, and implementation support.
The default prompt trigger is broad enough to match common user phrasing around productivity, workflows, Google Workspace, CLI, or implementation help, which increases the chance of implicit invocation when the user did not intend to call this skill. Because implicit invocation is enabled, this can cause unplanned routing to the skill, exposing the model to skill-controlled instructions and potentially producing irrelevant or unsafe actions in ordinary conversations.
