Work Productivity Multi Search Workflow Helper

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

Overview

This is a documentation-style workflow helper with overly broad activation hints, but it does not install code, persist, access credentials, or perform hidden actions.

Install this only if you want a broad workflow helper for multi-search-engine style productivity tasks. Be aware it may be selected for ordinary search or productivity prompts because its trigger language is loose; explicit invocation by skill name is safer than relying on automatic selection.

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: 92% confidence
• Finding: The trigger sentences are broad and generic enough to activate on common phrases like "multi," "search," or requests for a "practical workflow," which can cause the skill to be invoked outside its intended scope. In an agent ecosystem, over-broad activation can route unrelated user requests into this workflow, leading to incorrect behavior, prompt interference, or accidental execution of unsuitable instructions.

Vague Triggers

Medium

• Confidence: 95% confidence
• Finding: The trigger keywords and example invocation phrases are broad enough to match common terms like 'work-productivity', 'multi', 'search', and 'engine', which can cause accidental or excessive skill activation. In an agent ecosystem, unintended invocation can route unrelated user requests into this workflow, increasing the risk of incorrect actions, prompt confusion, or misuse of downstream tools.

Vague Triggers

High

• Confidence: 96% confidence
• Finding: The trigger keyword list includes extremely generic terms such as "multi," "search," "engine," and "bug fix," which are likely to appear in ordinary user requests unrelated to this skill. This can cause unintended activation, routing confusion, and prompt-surface expansion where the wrong skill is invoked and influences responses in inappropriate contexts.

Vague Triggers

High

• Confidence: 94% confidence
• Finding: The manifest description says to use the skill when a user asks for broad concepts like "work-productivity," "multi," "search," or needs almost any practical artifact or analysis support. This creates an overly permissive activation boundary that can match many benign conversations, increasing the chance of accidental invocation and unintended behavior transfer from this skill into unrelated tasks.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The example trigger sentences are written as common help requests and effectively teach broad natural-language activation patterns rather than precise invocation cues. If downstream systems or authors reuse these examples as matching guidance, the skill may activate on ordinary support phrasing and interfere with safer or more relevant skill selection.

Vague Triggers

High

• Confidence: 96% confidence
• Finding: The trigger list includes extremely broad everyday terms such as “multi”, “search”, and “engine”, which can cause the skill to activate in many unrelated conversations. Overbroad activation increases the chance that this skill intercepts requests outside its intended scope, leading to unintended behavior, prompt confusion, or unsafe workflow substitution.

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: The description says the skill should be used when the user mentions broad categories like work-productivity, multi, search, or engine, without defining clear limits. This makes routing ambiguous and can cause the skill to be selected for unrelated requests, increasing the risk of incorrect assistance and prompt-surface expansion.

Vague Triggers

High

• Confidence: 96% confidence
• Finding: The default prompt contains a very broad invocation phrase tied to common productivity and search-related wording, which can easily overlap with ordinary user requests. In systems that support automatic routing or prompt-based skill selection, this can cause the skill to activate unintentionally, exposing users to unexpected behavior and expanding the attack surface for prompt-injection or workflow hijacking through normal conversation.

Vague Triggers

High

• Confidence: 98% confidence
• Finding: Enabling implicit invocation without tight trigger constraints allows the platform to auto-select this skill from ambiguous user input. In this skill's broad 'work productivity' and 'multi search' context, that significantly increases the chance of unintended activation, which can lead to unauthorized tool use, misrouting of user requests, and easier exploitation via crafted phrasing intended to force this skill into a conversation.

Vague Triggers

High

• Confidence: 94% confidence
• Finding: The trigger phrases begin with very common language such as 'Help me' and 'I need', which makes the skill eligible to activate on many unrelated requests. In an agent environment, overly broad triggers can cause incorrect routing, unexpected invocation, and make it easier for a skill to intercept user tasks outside its intended scope.

VirusTotal

64/64 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.