Work Productivity Self Improving Workflow Helper

• Outcome: Pass
• Latest audit: Jul 29, 2026 · 7:51 AM UTC
• Version: 0.20260729.110214

Overview

This is a documentation-only workflow helper, with broad auto-invocation triggers that users should be aware of but no hidden execution, persistence, or data access.

Install only if you want a general helper for agent workflow improvement and bug-fix planning. Be aware that its broad trigger wording may cause it to activate for ordinary productivity or bug-fix requests, so explicit skill invocation or tighter routing would be safer.

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: 88% confidence
• Finding: The trigger sentences are broad enough to match ordinary user requests such as asking for help, practical workflows, or bug fixes, which can cause this skill to activate outside its intended scope. In an agent ecosystem, overbroad activation can route unrelated tasks into a self-improving workflow that may change behavior, generate misleading artifacts, or interfere with safer, more specific skills.

Vague Triggers

Medium

• Confidence: 95% confidence
• Finding: The trigger phrases are broad, generic, and overlap with ordinary user requests such as asking for help, practical workflows, or bug fixes. This can cause the skill to activate unintentionally in unrelated contexts, leading to inappropriate instruction injection into benign conversations and expanding the skill’s operational reach beyond user intent.

Vague Triggers

High

• Confidence: 97% confidence
• Finding: The skill description uses very broad activation terms such as 'self' and 'improving', which are common in unrelated user requests. This can cause the skill to activate outside its intended scope, leading to inappropriate routing, unintended instruction injection into unrelated workflows, or suppression of more relevant skills.

Vague Triggers

High

• Confidence: 99% confidence
• Finding: The keyword list contains generic everyday terms like 'self', 'improving', 'errors', and 'enable' that are highly likely to appear in benign, unrelated conversations. In an agent ecosystem, this creates trigger collisions that can invoke the skill unexpectedly, increasing the chance of misrouting, context pollution, and accidental application of workflow guidance where it does not belong.

Vague Triggers

Medium

• Confidence: 94% confidence
• Finding: The example trigger sentences reinforce an overly permissive activation model by demonstrating invocation from vague, reusable phrasing rather than narrowly scoped requests. This normalizes broad matching behavior and makes it more likely that downstream systems or authors will treat loosely related requests as valid triggers.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger list includes extremely broad everyday terms such as "self", "improving", "enable", and "bug fix", which can cause the skill to activate in many unrelated conversations. Over-broad activation increases the chance of unintended workflow injection, response hijacking, and user confusion because the agent may apply this skill outside its intended scope.

Vague Triggers

Medium

• Confidence: 87% confidence
• Finding: The description says to use the skill when users ask for broad themes like work-productivity, self, or improving, but it does not clearly define boundaries for when the skill should or should not engage. Ambiguous enablement rules can cause accidental invocation and make it easier for unrelated prompts to steer the agent into this workflow.

Vague Triggers

Medium

• Confidence: 85% confidence
• Finding: The default prompt and description use broad, generic phrasing about helping with 'work-productivity' and 'self-improving' workflows, which can cause the platform to invoke this skill for loosely related requests. Overbroad invocation increases the chance the skill is selected unexpectedly, exposing users to unintended behavior and expanding the attack surface for prompt or workflow misuse.

Vague Triggers

Medium

• Confidence: 94% confidence
• Finding: Enabling implicit invocation without clear trigger constraints allows the skill to be auto-selected in contexts the user may not intend. In a self-improving workflow skill, this is more dangerous because such skills may influence agent configuration, safety posture, or workflow behavior, so accidental invocation can have broader downstream effects than a simple read-only helper.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger sentences include generic phrases like 'Help me' and 'I need a practical workflow' combined with broad requirement text, which can cause the skill to activate for unrelated user requests. In an agent environment, overly broad activation increases the chance of accidental routing, context confusion, and unintended execution of this skill instead of a more appropriate one.

VirusTotal

64/64 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.