Back to skill

Security audit

Work Productivity Self Improving Workflow Helper

Security checks across malware telemetry and agentic risk

Overview

This is a low-risk workflow-helper skill with overly broad activation wording, but it does not install code, request credentials, persist, or perform hidden actions.

Before installing, consider narrowing or disabling implicit invocation if you do not want this helper to appear during ordinary productivity, bug-fix, or improvement requests. The inspected artifact otherwise behaves like a documentation/workflow aid rather than a privileged automation tool.

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

Vague Triggers

Medium
Confidence
95% confidence
Finding
The trigger examples are written so broadly that they can match ordinary user requests unrelated to this specific skill, increasing the chance of accidental activation. In an agent environment, overbroad activation can cause the wrong skill to take over a task, inject irrelevant workflow steps, and bypass the user's intended tool or narrower safeguards.

Vague Triggers

Medium
Confidence
96% confidence
Finding
The keyword list includes generic terms such as 'self', 'improving', 'reflection', and 'bug fix' that appear in many unrelated conversations, making unintended routing likely. In a multi-skill agent system, this can cause persistent misfires, unexpected instruction injection, and reduced trust in skill selection, especially because the skill presents itself as proactive and workflow-shaping.

Vague Triggers

Medium
Confidence
96% confidence
Finding
The trigger phrases are broad, generic, and include common words like "self", "improving", and "proactive", which can cause the skill to activate for many unrelated everyday requests. In an agent ecosystem, this increases the chance of unintended invocation, prompt shadowing, and misrouting user tasks into this workflow, potentially overriding more appropriate skills or causing confusing autonomous behavior.

Vague Triggers

High
Confidence
96% confidence
Finding
The trigger list includes extremely generic terms like "self," "improving," and "proactive," which are common in ordinary user requests and likely to cause unintended activation. Over-broad activation can route unrelated conversations through this skill, causing prompt hijacking of task selection, confusion, and unsafe execution of a workflow that was not actually requested.

Vague Triggers

High
Confidence
95% confidence
Finding
The manifest description says to use the skill whenever a user asks for broad concepts like work-productivity, self, improving, or proactive, which makes invocation ambiguous and overly expansive. In agent systems, vague routing criteria increase the chance that this skill is selected for unrelated requests, potentially overriding more appropriate safeguards or causing incorrect automation behavior.

Vague Triggers

Medium
Confidence
88% confidence
Finding
The example trigger sentences repeat broad language instead of demonstrating precise, distinguishable cases, reinforcing unsafe activation patterns. This makes it more likely that downstream implementers or routers will treat vague semantic similarity as sufficient to invoke the skill, increasing accidental activation and workflow misuse.

Vague Triggers

High
Confidence
94% confidence
Finding
The trigger list includes extremely broad everyday terms such as "self", "improving", and "proactive", which are likely to appear in many unrelated user requests. This can cause accidental invocation of the skill outside its intended scope, leading to prompt hijacking of routing behavior, irrelevant workflow injection, or unintended influence over conversations that were not asking for this capability.

Vague Triggers

Medium
Confidence
92% confidence
Finding
The default prompt and short description are extremely broad and overlap with common productivity requests, which increases the chance the skill will be invoked for routine user queries beyond its intended scope. Over-broad routing can expose users to unintended agent behavior, including unrequested workflow changes, proactive actions, or security-relevant guidance in contexts where the user did not explicitly ask for this skill.

Vague Triggers

Medium
Confidence
96% confidence
Finding
Allowing implicit invocation while the skill has broad activation semantics makes accidental triggering substantially more likely. If auto-invoked in unrelated conversations, the agent may apply proactive workflow behavior, recommendations, or artifacts without clear user consent, creating confusion, unsafe automation, or prompt-scope escalation.

Vague Triggers

High
Confidence
96% confidence
Finding
The trigger sentences and keywords are broad enough to match common, non-specific user requests such as asking for practical help, workflows, analysis, or implementation support. This can cause the skill to activate outside its intended scope, leading to unintended interception of ordinary prompts and potentially steering users into irrelevant or misleading workflow behavior.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.