Security audit

Work Productivity Proactive Agent Workflow Helper

Security checks across malware telemetry and agentic risk

Overview

This is a documentation-only workflow helper with overbroad activation wording, but it does not install code, persist, access credentials, or perform hidden actions.

This skill appears safe to install as a workflow helper, but users should be aware that its broad trigger words may make it appear in unrelated productivity or bug-fix requests. Prefer explicit invocation, or narrow the activation terms before publishing widely.

SkillSpector

By NVIDIA

Vulnerability Patterns

Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (8)

Vague Triggers

Medium

Confidence: 89% confidence
Finding: The trigger phrases are generic and overlap with common user requests such as asking for help, needing a workflow, or mentioning broad terms like 'task' or 'proactive'. This can cause unintended skill activation, leading the agent to apply this workflow in contexts the user did not explicitly intend, which is a security and reliability concern because it increases prompt-surface area and may override more appropriate safeguards or domain-specific handling.

Vague Triggers

Medium

Confidence: 93% confidence
Finding: The trigger phrases are broad enough to match ordinary productivity and help requests, which can cause the skill to activate when the user did not explicitly ask for it. In an agent ecosystem, this increases the chance of unintended workflow execution, prompt-context interference, or the skill shaping responses in situations outside its intended scope.

Vague Triggers

High

Confidence: 95% confidence
Finding: The trigger list includes very generic terms such as "proactive," "transform," "task," "needs," and "bug fix," which can match many unrelated user requests. This creates an overbroad auto-invocation surface where the skill may activate outside its intended scope, leading to unintended prompt injection exposure, workflow interference, or confused-deputy behavior in multi-skill environments.

Vague Triggers

High

Confidence: 91% confidence
Finding: The manifest description says to use the skill when a user asks for broad concepts like "work-productivity," "proactive," "transform," or "task," which are common across many benign conversations. An ambiguous invocation condition increases the chance the platform routes unrelated requests into this skill, expanding attack surface and causing misapplication of instructions or data handling in contexts the user did not intend.

Vague Triggers

High

Confidence: 95% confidence
Finding: The trigger list includes very common words such as "task", "needs", and "proactive", which can cause the skill to activate in many unrelated conversations. Over-broad activation increases the chance the agent injects irrelevant workflow guidance into contexts where it was not requested, creating unsafe routing and reducing user control.

Vague Triggers

Medium

Confidence: 88% confidence
Finding: The description says the skill should be used when users ask for broad categories like work-productivity, proactive, transform, or practical support, but it does not clearly define boundaries or exclusions. This ambiguity can cause the orchestrator or author to invoke the skill for loosely related requests, leading to misrouting and unintended behavior.

Vague Triggers

Medium

Confidence: 93% confidence
Finding: The manifest enables implicit invocation while using very broad, generic activation text such as 'work-productivity', 'proactive', 'task', and 'analysis'. This can cause the skill to trigger in contexts the user did not clearly intend, increasing the chance of unintended execution, prompt-context pollution, or the skill being selected for unrelated tasks.

Vague Triggers

High

Confidence: 95% confidence
Finding: The trigger sentences and keywords are so broad that they can match ordinary user requests unrelated to this specific skill, causing the skill to activate outside its intended scope. In an agent ecosystem, over-broad activation can lead to unintended workflow injection, user confusion, and bypass of more appropriate skills or safer routing logic.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.