Work Productivity Proactive Agent Workflow Helper

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

Overview

This is a documentation-style workflow helper with overly broad activation wording but no executable code, credential handling, persistence, or data exfiltration behavior.

Installers should be aware that this skill may be selected too often because of broad trigger words like task, needs, transform, and proactive. Review or narrow invocation settings if precise routing matters, but the artifact itself does not request sensitive access or perform actions automatically.

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: 89% confidence
• Finding: The trigger phrases are extremely broad and include generic terms like "proactive," "task," and "needs," which can cause this skill to activate in many unrelated contexts. In an agent ecosystem, over-broad activation can route sensitive or irrelevant user requests into the wrong workflow, increasing the chance of unsafe automation, user confusion, or prompt-surface abuse through unintended invocation.

Vague Triggers

High

• Confidence: 96% confidence
• Finding: The trigger phrases are broad enough to match ordinary productivity or task-oriented requests, which can cause this skill to activate outside the user's intent. In an agent ecosystem, overbroad invocation increases the chance of prompt/skill hijacking, unintended workflow substitution, and accidental exposure of user context to an irrelevant skill.

Vague Triggers

High

• Confidence: 97% confidence
• Finding: The skill description includes very broad trigger terms such as 'task', 'transform', and generic requests for a 'workflow, artifact, checklist, analysis, or implementation support'. This can cause the skill to activate in many unrelated contexts, increasing the chance of accidental routing, inappropriate guidance, or overshadowing a more suitable and safer specialized skill.

Vague Triggers

High

• Confidence: 99% confidence
• Finding: The keyword list contains vague single-word triggers including 'proactive', 'transform', 'task', and 'needs', which are common in ordinary conversation. Because they lack scope constraints, these triggers can match an extremely wide range of benign prompts, causing unintended invocation and potentially interfering with agent routing or prompting chains at scale.

Vague Triggers

High

• Confidence: 94% confidence
• Finding: The trigger keyword list includes very broad everyday terms such as 'task', 'needs', and 'partners', which can match many unrelated user requests. This can cause accidental activation of the skill in contexts where it is not appropriate, increasing the chance of irrelevant guidance, workflow hijacking, or unexpected prompt-scope expansion.

Vague Triggers

High

• Confidence: 91% confidence
• Finding: The description says to use the skill when a user asks for broad categories like 'work-productivity', 'proactive', 'transform', or 'task', which leaves activation boundaries unclear. Ambiguous activation criteria can cause the skill to be invoked for loosely related requests, leading to overreach and reducing user control over which behavior is applied.

Vague Triggers

Medium

• Confidence: 87% confidence
• Finding: The example trigger phrases are highly generic and effectively restate broad demand language without clarifying exact scope. Without precise examples and counterexamples, implementers may treat many vague requests as valid triggers, increasing false activations and inconsistent behavior.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The manifest description and default prompt use broad, generic phrasing like 'help me' and a wide set of loosely related trigger terms, which increases the chance the skill is invoked in contexts beyond its intended scope. Overbroad invocation language can cause unintended routing, exposing users to irrelevant or unsafe automation paths and reducing the reliability of skill selection.

Vague Triggers

High

• Confidence: 98% confidence
• Finding: Enabling implicit invocation without tight trigger constraints allows the platform to auto-select this skill for loosely matching requests. In combination with the broad productivity/proactive workflow framing, this can lead to unexpected activation, task interception, or execution in inappropriate contexts, which is especially risky for an agentic helper intended to transform workflows or produce implementation guidance.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger sentences and keywords are broad enough to match many ordinary productivity requests, which can cause this skill to activate outside its intended scope. In an agent ecosystem, overbroad activation can lead to unintended workflow injection, user confusion, and the application of this skill's assumptions to unrelated tasks.

VirusTotal

63/63 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.