Work Productivity Proactive Agent Workflow Helper

• Outcome: Pass
• Latest audit: Jul 29, 2026 · 3:39 AM UTC
• Version: 0.20260729.110214

Overview

This is a non-executable workflow helper with over-broad activation wording, but I found no hidden, destructive, credential-seeking, or data-exfiltrating behavior.

Install only if you want a general proactive-agent workflow helper. Be aware it may be invoked too often because its trigger terms are broad; prefer explicit invocation by skill name when using it.

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

Vague Triggers

High

• Confidence: 92% confidence
• Finding: The trigger sentences and keywords are broad, generic, and closely resemble ordinary user requests, which can cause the skill to activate unintentionally in unrelated contexts. In an agent ecosystem, this increases the chance of prompt/skill hijacking or misrouting user tasks into this workflow, especially because terms like 'help me', 'practical workflow', 'task', and 'bug fix' are common across many benign conversations.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The trigger phrases are broad and include generic terms such as "proactive," "task," and "needs," which can cause the skill to activate in contexts far beyond its intended scope. In an agent environment, overly broad routing increases the chance of accidental invocation, unintended workflow execution, and user confusion, especially because the skill is designed to transform requests into actionable workflows.

Vague Triggers

High

• Confidence: 96% confidence
• Finding: The skill description says to use the skill when a user asks for very broad terms like "work-productivity," "proactive," "transform," or "task," which are common in ordinary conversation and not tightly scoped to this skill's niche purpose. This can cause unintended invocation, leading the agent to route unrelated requests into this skill and potentially override more appropriate safety, domain, or task-specific handling.

Vague Triggers

High

• Confidence: 98% confidence
• Finding: The keyword trigger list includes generic words such as "proactive," "transform," "task," "needs," and "bug fix," which are so common that they can match a wide range of unrelated prompts. In an agentic environment, ambiguous auto-invocation increases the chance of misrouting user requests, unnecessary context injection, and unexpected behavior across many conversations.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The example trigger sentences reinforce permissive activation by showing the skill being invoked from vague, everyday phrasing rather than from explicit, intentional requests. This trains routing behavior toward overmatching and makes accidental activation more likely, especially when examples are used as few-shot cues by upstream systems.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger list includes very broad, common terms such as 'task', 'needs', and 'partners', which can cause the skill to activate in many unrelated conversations. This increases the chance of unintended routing, unexpected behavior, and accidental application of this skill's workflow in contexts where it was not requested.

Vague Triggers

Medium

• Confidence: 87% confidence
• Finding: The description states the skill should be used for broad categories like work-productivity, proactive-agent, proactive, transform, and task, but does not clearly define decision boundaries for when the skill should or should not activate. Ambiguous activation criteria can lead to over-triggering and misclassification of user intent, reducing predictability and safety of skill selection.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The manifest description and default prompt use broad, vague language that can cause the skill to be invoked in many loosely related contexts rather than only when clearly intended. Because implicit invocation is enabled, this ambiguity increases the chance of accidental activation, which can lead to inappropriate handling of user tasks, prompt-scope confusion, or unintended access to workflow context.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The trigger examples are generic enough to match ordinary productivity requests, which can cause the skill to activate outside its intended scope. In an agent ecosystem, over-broad routing increases the chance of inappropriate delegation, confused behavior, and accidental application of this workflow to unrelated user tasks.

VirusTotal

58/58 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.