Work Productivity Proactive Agent Workflow Helper

• Outcome: Pass
• Latest audit: Jul 29, 2026 · 6:37 AM UTC
• Version: 0.20260729.110214

Overview

This is a documentation-style workflow helper with no executable code or hidden data access, though its activation wording is overly broad.

Use this if you want a lightweight helper for proactive-agent workflow planning. Consider disabling implicit invocation or invoking it by name if you do not want generic productivity requests routed into this skill.

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: 90% confidence
• Finding: The trigger examples are broad, generic, and partially truncated, which can cause the skill to activate for loosely related requests rather than clear user intent. In an agent workflow context, overbroad activation increases the chance of unsolicited workflow execution, irrelevant guidance, or unintended handling of user tasks, making the skill less predictable and potentially unsafe when chained with other agent behaviors.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The trigger phrases and keywords are broad enough to match common, everyday requests like 'task', 'transform', or 'help me', which can cause the skill to activate unintentionally. In an agent workflow context, unintended invocation can route user requests into the wrong automation path, causing misleading outputs, unnecessary actions, or accidental exposure of workflow behavior where it was not requested.

Vague Triggers

High

• Confidence: 97% confidence
• Finding: The trigger list includes generic terms such as "proactive," "transform," "task," "needs," and "bug fix," which are common in ordinary conversations and likely to match unrelated user requests. This can cause accidental invocation or over-selection of the skill, leading to misrouting, unexpected behavior, and increased exposure to any downstream unsafe instructions or poor workflow assumptions.

Vague Triggers

High

• Confidence: 98% confidence
• Finding: The manifest description says to use the skill when a user asks for broad categories like work-productivity, proactive, transform, task, or practical workflow support, which is too ambiguous for safe routing. An overly broad activation description increases the chance the skill is selected for unrelated prompts, where it may produce irrelevant guidance or interfere with more appropriate skills and controls.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The example trigger phrases are truncated and malformed, so they do not clearly demonstrate when the skill should or should not activate. Poor examples weaken routing discipline and make it more likely that implementers or automated systems infer an overly broad trigger scope from incomplete phrases.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger list includes broad everyday terms such as "task", "needs", and "partners", which can cause the skill to activate in many unrelated conversations. In an agent environment, overbroad activation can hijack routing, produce irrelevant actions, and increase the chance that this skill handles requests outside its intended scope.

Vague Triggers

Medium

• Confidence: 88% confidence
• Finding: The description says to use the skill when users ask for broad categories like work-productivity, proactive, transform, or practical support, but it does not define clear inclusion and exclusion criteria. This ambiguity makes accidental invocation more likely, especially because the skill is framed as generally useful for workflows, checklists, analysis, and implementation support.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The default prompt is written as a broad natural-language trigger tied to common work/productivity requests, which can cause the skill to activate in situations beyond the user's explicit intent. In a proactive-agent workflow context, that increases the chance of unintended delegation, prompt injection exposure, or inappropriate assistance being inserted into ordinary conversations.

Vague Triggers

Medium

• Confidence: 95% confidence
• Finding: Enabling implicit invocation without defined activation boundaries allows the platform to auto-select this skill for loosely related requests. Because this skill is framed broadly around proactive workflows and practical implementation help, unintended invocation could expose users to unreviewed automation behavior or broaden the attack surface for malicious prompt content in normal user tasks.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger sentences and keywords are broad enough to match common user phrasing such as 'help me', 'practical workflow', 'task', or 'transform', which can cause the skill to activate outside its intended scope. In an agent environment, overbroad activation can route unrelated requests into this skill, creating confused-deputy behavior, reducing user control, and increasing the chance that other safety-relevant instructions are bypassed or overshadowed.

VirusTotal

64/64 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.