Security audit

Work Productivity Skill Vetter Workflow Helper

Security checks across malware telemetry and agentic risk

Overview

This is a documentation-only workflow helper with overly broad activation wording but no executable code, credential handling, persistence, or hidden data access.

Install only if you want a Skill Vetter-style workflow helper. Be aware it may be selected for unrelated requests containing generic words such as security, github, before, or bug fix; explicit invocation is safer until the trigger wording is narrowed.

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: 90% confidence
Finding: The trigger sentences and keywords are broad enough to activate on generic terms like 'security', 'first', 'github', or 'bug fix', which can cause the skill to be invoked outside its intended scope. In an agent environment, overbroad activation can redirect user workflows, cause unintended handling of sensitive tasks, or bypass more appropriate specialized skills.

Vague Triggers

Medium

Confidence: 88% confidence
Finding: The trigger phrases are broad enough to match generic terms like 'security', 'first', 'github', or 'bug fix', which can cause the skill to activate in unintended contexts. In an agent ecosystem, overbroad activation can route unrelated user requests into this workflow, leading to incorrect guidance, prompt hijacking surface expansion, or accidental execution of a security-oriented process when it was not requested.

Vague Triggers

High

Confidence: 97% confidence
Finding: The trigger list includes highly generic terms such as "security," "first," "before," and "github," which can cause the skill to activate in many unrelated conversations. Overbroad activation increases the chance this skill intercepts requests outside its intended scope, leading to incorrect routing, unexpected behavior, or security-relevant workflow confusion when users did not intend to invoke it.

Vague Triggers

High

Confidence: 95% confidence
Finding: The description says to use the skill when a user asks for broad concepts like "security," "first," or any practical workflow or checklist, which is far wider than the skill's stated job-to-be-done. This ambiguous invocation condition can cause the system to select the skill in unrelated contexts, potentially overshadowing more appropriate skills and creating unsafe or misleading task handling.

Vague Triggers

High

Confidence: 96% confidence
Finding: The trigger list includes very broad, common terms such as "security", "first", "before", and "github", which can cause the skill to activate in many unrelated conversations. Over-broad activation can route users into the wrong workflow, leading to confused task handling, unsafe automation suggestions in the wrong context, or interference with other more appropriate skills.

Vague Triggers

Medium

Confidence: 89% confidence
Finding: The description says to use the skill whenever a user asks for broad categories like work-productivity, security, or practical workflow support, but it does not define clear boundaries for when the skill should not activate. This ambiguity increases the chance of accidental invocation and inappropriate delegation, especially because the skill overlaps with many ordinary support and security-related requests.

Vague Triggers

Medium

Confidence: 94% confidence
Finding: The default prompt contains broad, generic phrasing such as 'help me' and references common concepts like productivity, security, workflows, checklists, and implementation support. Combined with allow_implicit_invocation: true, this increases the chance the skill is triggered in contexts the user did not explicitly intend, causing unintended routing of requests and possible overexposure of the skill in unrelated conversations.

Vague Triggers

High

Confidence: 95% confidence
Finding: The trigger sentences and keywords are broad enough to match many ordinary requests about productivity, security, GitHub, bug fixes, or "before installing," which can cause this skill to activate outside its intended scope. Over-broad activation is dangerous because it can hijack unrelated workflows, suppress more appropriate skills, and increase the chance that users receive generic or mismatched guidance in security-sensitive contexts.

VirusTotal

63/63 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.