Work Productivity Proactive Agent Workflow Helper

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

Overview

This is a documentation-only workflow helper with no executable code, but its automatic invocation wording is too broad and may trigger in unrelated tasks.

Before installing, be aware that this skill may activate for generic productivity or task-help requests. Prefer explicit invocation by skill name, and consider narrowing or disabling implicit invocation if your environment has many skills competing for routing.

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: 91% confidence
• Finding: The trigger phrases are broad and overlap with common productivity/help-seeking language, which increases the chance the skill is invoked when the user did not explicitly intend it. In an agent ecosystem, unintended invocation can cause the wrong workflow to steer task execution, inject irrelevant instructions, or bypass more appropriate user-selected skills.

Vague Triggers

High

• Confidence: 94% confidence
• Finding: The trigger phrases are broad enough to match many ordinary user requests such as asking for help, workflows, tasks, or bug fixes, which can cause the skill to activate outside its intended scope. In an agent ecosystem, overbroad invocation increases the chance of unintended workflow capture, prompt interference, and incorrect routing of user requests into this skill.

Vague Triggers

High

• Confidence: 96% confidence
• Finding: The trigger list includes very generic words such as "task," "needs," and "proactive," which are likely to appear in ordinary user requests unrelated to this skill. That can cause unintended activation, leading the agent to apply the wrong workflow or inject irrelevant behavior into unrelated tasks, especially in systems that auto-select skills from keyword matches.

Vague Triggers

High

• Confidence: 93% confidence
• Finding: The description says to use the skill when a user asks for broad concepts like "work-productivity," "task," or any "practical workflow, artifact, checklist, analysis, or implementation support," which is far too open-ended for safe routing. In an agent environment, this ambiguity increases the chance of the skill being selected for many unrelated requests, potentially overriding more appropriate skills or causing confusing, unsafe, or low-quality outputs.

Vague Triggers

High

• Confidence: 94% confidence
• Finding: The trigger list includes very broad everyday terms such as "task", "needs", and "partners", which can cause the skill to activate in many unrelated conversations. In an agent ecosystem, unintended invocation can steer user workflows, inject irrelevant instructions, or override a more appropriate skill, creating reliability and safety issues even without overtly malicious content.

Vague Triggers

Medium

• Confidence: 88% confidence
• Finding: The applicability description is broad and lacks clear boundaries for when the skill should not be used. This ambiguity increases the chance of accidental routing to the skill, which can degrade system behavior and expose users to workflow guidance that does not fit their request.

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: The default prompt embeds a very broad invocation phrase tied to generic terms like work-productivity, proactive, task, workflow, checklist, and analysis, which can overlap with ordinary user requests. This increases the chance the skill is invoked in contexts the user did not explicitly intend, causing unintended prompt injection of the skill’s behavior and potentially exposing users to incorrect or over-broad automation.

Vague Triggers

Medium

• Confidence: 96% confidence
• Finding: Enabling implicit invocation without strict trigger constraints allows the platform to auto-activate this skill based on ambiguous language rather than deliberate user selection. In this skill, the metadata and description are broad and catch many common productivity requests, making accidental routing and unintended execution materially more likely.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger sentence is so broad and generic that it could match ordinary user requests unrelated to this skill’s intended scope, causing unintended invocation. In agent ecosystems, overbroad activation can route user input into the wrong workflow, leading to confusion, irrelevant actions, or accidental execution of planning behavior in contexts where it was not requested.

Vague Triggers

Medium

• Confidence: 97% confidence
• Finding: The activation examples do not sufficiently constrain invocation conditions, so the skill may be selected for loosely related terms like 'help me' or generic workflow requests. This increases the chance of skill hijacking or inappropriate routing, especially in multi-skill environments where broad matching can suppress more appropriate and safer skills.

VirusTotal

64/64 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.