Back to skill

Security audit

Work Productivity Self Improving Workflow Helper

Security checks across malware telemetry and agentic risk

Overview

This is a documentation-style workflow helper with no executable code, credential handling, persistence, or destructive behavior, though its activation triggers are overly broad.

This skill appears safe to install as a workflow helper, but users should be aware it may activate too broadly for ordinary requests involving logs, improvements, or bug fixes. Prefer explicit invocation when possible, and maintainers should narrow the trigger terms to self-improving agent workflow or agent reliability contexts.

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
94% confidence
Finding
The trigger phrases are broad enough to match ordinary user requests about help, workflows, bug fixes, or improvements, which can cause unintended activation of this skill outside its intended scope. In an agent ecosystem, overbroad routing can misdirect user tasks, increase exposure to unsafe instructions from the wrong skill, and make downstream behavior less predictable.

Vague Triggers

Medium
Confidence
95% confidence
Finding
The trigger phrases are very broad and include generic terms like "self," "improving," "logs," and "bug fix," which can cause the skill to activate for many ordinary requests unrelated to this skill’s intended scope. In an agent ecosystem, overbroad activation can misroute user tasks, increase unintended invocation frequency, and create opportunities for prompt/context capture from unrelated workflows.

Vague Triggers

High
Confidence
97% confidence
Finding
The trigger list includes extremely broad everyday terms such as "self," "logs," "own," and "improvement," which can cause the skill to activate in many unrelated conversations. That increases the chance of unintended routing, context hijacking, or the skill influencing tasks it was not meant to handle, especially because this skill outputs workflows and implementation guidance that may shape subsequent agent behavior.

Vague Triggers

High
Confidence
95% confidence
Finding
The description says to use the skill when a user asks for broad terms like "work-productivity," "self," "improving," or "logs," which is ambiguous and substantially over-expands the activation surface. In an agent ecosystem, that can lead to accidental invocation on benign requests and let this skill override more appropriate tooling or inject unnecessary workflow guidance into unrelated tasks.

Vague Triggers

High
Confidence
95% confidence
Finding
The trigger list includes very common words such as "self", "improving", "logs", and "own", which can cause the skill to activate in many unrelated conversations. Over-broad activation increases the chance that this skill intercepts requests outside its intended scope, leading to unsafe or misleading automation, prompt-routing errors, and reduced user control.

Vague Triggers

Medium
Confidence
88% confidence
Finding
The activation description says the skill should be used for broad categories like work-productivity, self, improving, and logs, without clearly defining exclusions or required context. This ambiguity makes accidental invocation more likely and can route unrelated user requests into an autonomous workflow-improvement skill, creating confusion, overreach, or unintended actions.

Vague Triggers

Medium
Confidence
90% confidence
Finding
The default prompt contains a broad, natural-language trigger phrase that can match common user requests about productivity, workflows, logs, or improving setup, making unintended invocation more likely. Because implicit invocation is enabled, the skill may activate in contexts the user did not explicitly intend, which can lead to confusing behavior, over-broad tool use, or accidental exposure of this skill's capabilities in unrelated conversations.

Vague Triggers

Medium
Confidence
95% confidence
Finding
The trigger sentences are broad, natural-language phrases that can match ordinary user requests and cause the skill to activate when the user did not explicitly intend to invoke it. In an agent ecosystem, overbroad activation can route unrelated conversations into this skill, producing incorrect automation, confusion, or unsafe follow-on actions based on the wrong workflow.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.