Security audit

Work Productivity Multi Search Workflow Helper

Security checks for vulnerabilities and agentic risk

Overview

This is a low-authority workflow/documentation skill, though its activation language is too broad and may trigger unintentionally.

Before installing, be aware that this skill may activate for ordinary search or workflow requests because its triggers are broad and implicit invocation is enabled. It appears safe as a documentation/workflow helper, but users who prefer precise routing should narrow the trigger phrases or disable implicit invocation.

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 trigger phrases are extremely broad (multi, search, engine, integration, bug fix) and include generic natural-language prompts that could cause the skill to activate in many unrelated conversations. In an agent ecosystem, overbroad activation can route user requests into the wrong workflow, causing unintended tool use, irrelevant instructions, or unsafe automation in contexts the user did not intend.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 94% confidence
Finding: The description says to use the skill when a user asks for broad terms like "work-productivity," "multi," "search," or "engine," or whenever they need a practical workflow, artifact, checklist, analysis, or implementation support. These conditions are so expansive that they can match many unrelated requests, making accidental invocation and privilege overreach more likely in an agentic environment.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The trigger list includes extremely generic terms such as "multi", "search", "engine", "global", and "supports", which are common in many unrelated prompts. This can cause the skill to activate outside its intended scope, increasing the chance of prompt hijacking, incorrect tool selection, or unintended routing of user requests into this workflow.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The trigger list includes extremely broad, high-frequency terms such as "multi", "search", and "engine", which can cause the skill to activate for many unrelated requests. In an agent environment, unintended invocation can redirect workflows, produce irrelevant or conflicting actions, and increase the chance that this skill handles tasks outside its intended safety and quality boundaries.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The trigger phrases are extremely broad and include common terms like "multi," "search," and "engine," which can cause the skill to activate in contexts far outside its intended purpose. In an agent environment, over-broad routing can misapply workflow instructions to unrelated user requests, increasing the chance of unintended actions, confused task execution, or unsafe delegation.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 88% confidence
Finding: This file is labeled as a Chinese README, but key user-facing sections such as the title, requirement description, workflow description, keywords, and trigger phrases are primarily in English. That creates a language-policy inconsistency and effectively forces mixed-language usage without user opt-in or justification.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 81% confidence
Finding: 文件名和正文均表明该技能内容固定为 zh-CN 中文版本，但文中未说明这是可选语言，也未向用户提供语言偏好选择或切换机制。对于面向广泛用户群体的技能，这可能构成未获用户同意即施加特定语言/地区设置的自然语言策略问题。
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 92% confidence
Finding: The description says to use the skill when users mention broad categories like work-productivity, multi, search, or engine, or when they need practical support, but it does not define clear boundaries or exclusions. This ambiguity increases the likelihood of over-triggering and misrouting, especially because the terms overlap with many benign, unrelated user requests.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 94% confidence
Finding: The default prompt contains a very broad invocation phrase tied to common workplace and search-related language, which increases the chance of the skill being triggered during ordinary user requests rather than deliberate invocation. In combination with an assistant environment, this can cause unintended routing, context injection into the skill, or accidental execution of workflows the user did not explicitly request.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: Enabling implicit invocation without strict trigger constraints means the platform may auto-select this skill based on ambiguous user language. Because the skill targets broad productivity and search workflows, the lack of gating makes accidental activation more likely and can expose user context to a skill that was not intentionally chosen.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The trigger terms and example trigger sentences are overly broad and include common words like "multi," "search," and "engine," plus generic help-seeking phrasing. This can cause the skill to activate for unrelated requests, creating prompt-routing confusion and increasing the chance that users receive the wrong workflow or that a more privileged/less appropriate skill is invoked unintentionally.
Content: No source excerpt is available for this finding.