Work Productivity Multi Search Workflow Helper

• Outcome: Pass
• Latest audit: Jul 29, 2026 · 4:51 AM UTC
• Version: 0.20260729.110214

Overview

This is a documentation-only workflow helper with overbroad activation wording, but no hidden execution, data access, persistence, or destructive behavior.

Installers should understand that the skill may activate on ordinary search-related requests because its trigger terms are too generic. Use explicit invocation or narrow the triggers if accidental activation would disrupt your workflow.

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

Vague Triggers

Medium

• Confidence: 88% confidence
• Finding: The trigger phrases are very broad and include generic terms like "multi", "search", and "engine", which can cause the skill to activate in unrelated contexts. In an agent environment, overly permissive activation boundaries can route unintended user requests into this workflow, causing mis-execution, confusion, or unsafe application of the skill outside its intended scope.

Vague Triggers

High

• Confidence: 93% confidence
• Finding: The trigger phrases are broad, generic, and include common terms like "multi", "search", and "engine", making accidental invocation likely during ordinary user requests. In an agent skill ecosystem, overbroad activation can route unrelated tasks into this workflow, causing unintended behavior, user confusion, and possible unsafe chaining with other capabilities.

Vague Triggers

High

• Confidence: 94% confidence
• Finding: The trigger keyword list includes highly generic terms such as "multi", "search", and "engine", which are common in ordinary user requests and can cause the skill to activate outside its intended scope. Over-broad invocation increases the chance of incorrect routing, prompt-context pollution, and unintended use of the skill in unrelated tasks.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The manifest description says to use the skill whenever a user asks for broad topics like work-productivity, search, engine, or any practical workflow or analysis support, which is far wider than a safely bounded capability definition. This ambiguity can cause inappropriate automatic selection of the skill, leading to user confusion, incorrect assistance, and exposure of irrelevant instructions into agent decision-making.

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: The example trigger sentences are repetitive and vague, and they model activation on broad descriptive text instead of precise user intents. This reinforces accidental invocation patterns and makes it more likely that matching systems or users will call the skill in contexts only loosely related to its real function.

Vague Triggers

High

• Confidence: 96% confidence
• Finding: The trigger list includes very generic terms such as "multi", "search", "engine", and "global", which are common in unrelated user requests. This can cause accidental activation of the skill in contexts it was not designed for, leading to prompt-routing errors, irrelevant behavior, and possible interference with safer or more appropriate skills.

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: The description says to use the skill whenever a user mentions broad terms like work-productivity, multi, search, or engine, or whenever they need practical support around the requirement. These activation conditions are underspecified and expansive, increasing the chance of over-triggering and misclassification rather than a direct code-execution issue.

Vague Triggers

Medium

• Confidence: 94% confidence
• Finding: The default prompt/invocation text is broad and matches common work-related language such as 'help me' and generic productivity/search terms without clear boundaries. This can cause unintended implicit invocation of the skill in unrelated conversations, expanding the skill's access and influence beyond user intent and potentially routing sensitive business context into the skill unexpectedly.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger sentence is overly broad and resembles ordinary user language, which can cause the skill to activate in contexts where the user did not explicitly intend to invoke it. In an agent ecosystem, unintended invocation can route user requests into the wrong workflow, causing prompt hijacking of task selection, confusion, or inappropriate handling of unrelated requests.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The invocation guidance is ambiguous because it does not clearly define when the skill should be used versus when it should not, and the listed triggers are broad enough to overlap with many unrelated tasks. This increases the chance of accidental selection by an orchestrating agent, which can degrade safety and reliability by applying the wrong workflow to user input.

VirusTotal

64/64 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.