Work Productivity Multi Search Workflow Helper

• Outcome: Pass
• Latest audit: Jul 24, 2026 · 5:15 PM UTC
• Version: 0.1.0

Overview

This is a documentation-only workflow helper with overly broad auto-invocation signals, but it does not request privileged access, persistence, credentials, or hidden execution.

Before installing, be aware that this skill may be selected for generic search or workflow requests because its triggers are broad. It appears safe as a documentation helper, but maintainers should narrow the trigger terms or disable implicit invocation to avoid irrelevant activation.

SkillSpector

By NVIDIA

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

Vague Triggers

Medium

• Confidence: 94% confidence
• Finding: The trigger phrases are broad, natural-language prompts that can match many ordinary user requests unrelated to this specific skill. That increases the chance of unintended auto-invocation, causing the agent to route users into the wrong workflow, produce irrelevant outputs, or bypass more appropriate skills.

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: The invocation description lists generic keywords and broad usage language without clear scope boundaries, making it easy for unrelated requests containing words like 'search', 'engine', or 'help' to activate the skill. In an agentic environment, ambiguous routing can lead to incorrect tool selection, workflow confusion, and reduced safety if the skill is used outside its intended context.

Vague Triggers

High

• Confidence: 93% confidence
• Finding: The trigger phrases are broad and closely resemble normal user requests, which can cause the skill to activate unintentionally for unrelated conversations. In an agent ecosystem, accidental invocation can route user input into the wrong workflow, causing misleading outputs, unnecessary tool use, or unsafe automation in contexts the user did not intend.

Vague Triggers

High

• Confidence: 97% confidence
• Finding: The trigger keywords are extremely broad, including generic terms like "multi," "search," "engine," and "bug fix," which are likely to appear in many unrelated user requests. This can cause the skill to activate outside its intended scope, leading to prompt hijacking of normal workflows, unintended tool selection, or unsafe delegation based on weak relevance.

Vague Triggers

High

• Confidence: 96% confidence
• Finding: The description says to use the skill when a user asks for broad categories like "work-productivity," "multi," "search," or any practical workflow or analysis support, which creates an overly permissive invocation condition. In an agent environment, such vague routing criteria can cause this skill to capture unrelated requests and influence outputs in contexts where it was not intended or reviewed.

Vague Triggers

Medium

• Confidence: 88% confidence
• Finding: The example trigger sentence is vague and natural-language generic, making it easy for ordinary conversation to resemble an activation phrase. This increases accidental invocation risk and reinforces the already broad matching behavior, though the example itself is less dangerous than the keyword and description-level scope issues.

Vague Triggers

High

• Confidence: 97% confidence
• Finding: The trigger list includes extremely generic terms such as "multi", "search", and "engine", which can cause the skill to activate for many unrelated requests. Over-broad activation increases the chance that the wrong skill handles user input, leading to unsafe workflow substitution, confused-deputy behavior, or unintended disclosure of context to a skill not specifically requested.

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: The skill description says it should be used when users mention broad categories like work-productivity, multi, search, or engine, without clear boundaries on scope. This ambiguity makes accidental invocation more likely and can route unrelated tasks into this skill, reducing reliability and potentially exposing user context or causing inappropriate actions under the wrong workflow.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The default prompt is overly broad and generic, so the skill can be invoked in situations that only loosely match the intended use case. In an agent ecosystem, this increases the chance of unintended routing, context leakage, or the skill influencing tasks outside its safe scope, especially because the prompt text is truncated and not anchored to precise user intents.

Vague Triggers

High

• Confidence: 98% confidence
• Finding: Enabling implicit invocation without narrow trigger constraints allows the platform to auto-select this skill for loosely related requests. Because this skill advertises a broad work-productivity and multi-search workflow scope, implicit invocation can cause overreach, unintended execution, and exposure of user context to a skill that was not explicitly requested.

Vague Triggers

High

• Confidence: 93% confidence
• Finding: The trigger sentence is malformed and begins with an extremely broad phrase ('Help me'), which can cause the skill to activate for many unrelated user requests. In an agent-routing context, overly broad invocation patterns can misroute tasks, override more appropriate skills, and increase the chance of unsafe or unintended workflow execution.

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: This trigger remains ambiguous because it uses generic wording ('I need a practical workflow') and then appends awkward context that does not reliably constrain activation. Such ambiguity can cause accidental invocation on ordinary productivity requests, reducing routing precision and potentially exposing users to irrelevant or risky automation paths.

Vague Triggers

Medium

• Confidence: 95% confidence
• Finding: The invocation guidance as a whole lacks a well-defined trigger scope and includes malformed examples that are both broad and difficult to interpret. In a skill ecosystem, this increases the risk of systematic overmatching, where the skill is selected for unrelated prompts and may interfere with safer or more relevant skills.

VirusTotal

64/64 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.