Work Productivity Pollyreach Gives Workflow Helper

• Outcome: Pass
• Latest audit: Jul 24, 2026 · 6:53 PM UTC
• Version: 0.1.0

Overview

This is a documentation-only workflow helper with overly broad activation wording, but it does not request hidden access, persistence, credentials, destructive behavior, or external execution.

Before installing, be aware that this skill may activate too easily because its trigger terms are generic. It appears safe as a workflow helper, but users or publishers should narrow the triggers if precise routing matters.

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

High

• Confidence: 92% confidence
• Finding: The trigger phrases are excessively broad and include generic terms like 'every', 'phone', 'number', 'ability', and 'things', which can cause the skill to activate for unrelated user requests. In an agent ecosystem, overbroad activation can misroute tasks, override more appropriate skills, and create unsafe or confusing workflow execution from irrelevant prompts.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The trigger set includes highly generic terms such as “every”, “phone”, “number”, “ability”, “things”, and “done”, which can match many unrelated user requests and cause unintended activation of this skill. In an agent ecosystem, overly broad invocation can route sensitive or irrelevant tasks into the wrong workflow, increasing the chance of incorrect automation, confusing outputs, or accidental execution of follow-on steps under the wrong context.

Vague Triggers

High

• Confidence: 96% confidence
• Finding: The trigger list includes generic everyday terms such as 'every', 'phone', 'number', 'ability', 'things', and 'done', which can cause the skill to activate in many unrelated conversations. This creates an over-broad routing surface where users may be unexpectedly steered into this skill, increasing the chance of inappropriate context capture, user confusion, or interference with higher-priority/specialized skills.

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: The example trigger sentences are vague and closely mirror ordinary user requests, without clear scoping or disambiguation criteria. In systems that use examples to guide invocation, this can widen matching behavior beyond the intended domain and cause accidental activation on unrelated prompts, reducing reliability and potentially exposing user inputs to the wrong workflow logic.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger list includes extremely generic terms like 'every', 'phone', 'number', 'ability', 'things', and 'done', which are likely to appear in many unrelated conversations. This creates a high risk of accidental skill invocation, causing the agent to route tasks into this skill inappropriately and potentially override more relevant or safer skills.

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: The description says to use the skill when users mention broad topics like work-productivity or need any practical workflow, checklist, analysis, or implementation support for the requirement, which is too ambiguous. Overbroad activation guidance increases routing collisions and can cause the skill to activate outside its intended scope, degrading reliability and potentially exposing users to irrelevant instructions.

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: The sample trigger phrases are written as very generic help requests and closely resemble normal user prompts. If examples are too broad, they reinforce permissive matching behavior and make accidental invocation more likely in ordinary conversations unrelated to this skill.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The default prompt contains a very broad natural-language trigger phrase tied to common productivity terms, and the policy explicitly allows implicit invocation. That combination can cause the skill to activate during ordinary user requests unrelated to the intended workflow, creating prompt-routing confusion and unintended execution of the skill's behavior.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger keywords include extremely generic terms such as "gives," "every," "phone," and "things," which are common in ordinary user requests and are not uniquely tied to this skill. This can cause the skill to activate unexpectedly for unrelated prompts, leading to incorrect routing, prompt-surface expansion, and accidental invocation of workflow behavior outside the intended PollyReach-style use case.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The trigger sentence is vague and truncated, and it begins with a broad phrase like "Help me" that appears in many benign requests. Because it is insufficiently scoped to the skill’s actual domain, it increases the chance of false activations and unintended tool selection, especially in systems that rely on pattern matching for dispatch.

VirusTotal

63/63 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.