Work Productivity Skillscan Security Workflow Helper

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

Overview

This is a documentation-only workflow helper with overly broad auto-activation wording, but it does not contain executable code, credential handling, persistence, or data exfiltration.

Install only if you want this helper to be available for SkillScan-style workflow and checklist tasks. Be aware that its activation metadata is broad, so it could appear for generic security or bug-fix prompts; explicit invocation is safer than relying on automatic selection.

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

High

• Confidence: 95% confidence
• Finding: The trigger keywords and example activation phrases are excessively broad, including generic terms like "security," "gate," "every," and "bug fix." This can cause the skill to activate in many unrelated contexts, increasing the chance it intercepts prompts unexpectedly and influences workflows the user did not intend to delegate to this skill.

Vague Triggers

High

• Confidence: 97% confidence
• Finding: The trigger keywords and example phrases are extremely broad, including common words like "security," "every," "must," "before," and "bug fix." This can cause the skill to activate in many unrelated conversations, leading to unintended routing, prompt hijacking of normal user requests, and overreach into contexts the user did not explicitly authorize.

Vague Triggers

High

• Confidence: 96% confidence
• Finding: The trigger keywords are excessively broad and include common terms like 'security', 'every', 'must', 'before', and 'bug fix', which can cause this skill to activate in many unrelated conversations. In an agent environment, unintended activation can override more appropriate skills, inject irrelevant workflow steps, and expand the attack surface for prompt-routing abuse or policy confusion.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The description states the skill should be used when a user asks for broad categories such as 'work-productivity', 'security', or 'analysis', which are common across many benign requests. This ambiguity makes routing unpredictable and can lead to accidental invocation in contexts where the skill is not appropriate, increasing the risk of misexecution, user confusion, and prompt-scope interference.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The example trigger sentences repeat the same vague, catch-all phrasing instead of showing precise activation boundaries, reinforcing overbroad matching behavior. This makes the skill more likely to be selected for loosely related prompts and normalizes ambiguous routing rules, which can degrade reliability and create opportunities for unintended skill chaining.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger keywords are overly broad and include generic terms such as 'security', 'every', 'must', 'pass', and 'before', which can cause the skill to activate in many unrelated conversations. In an agent environment, this increases the chance of incorrect routing, unintended instruction injection into unrelated tasks, and user confusion about why this skill was selected.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The description says the skill should be used when users ask for broad categories like work-productivity, skillscan, security, gate, or every, or when they need practical workflow or checklist support, but it does not clearly bound what requests qualify. This ambiguity can lead to overmatching and misselection of the skill, which may inject irrelevant process guidance into unrelated requests.

Vague Triggers

High

• Confidence: 96% confidence
• Finding: The skill enables implicit invocation while using a very broad default prompt and description tied to common productivity and security-help language. This can cause the skill to be auto-selected in unrelated conversations, creating unintended execution paths, context leakage, or unsafe tool influence without clear user intent. The context makes this more dangerous because the skill claims applicability to broad workflow, checklist, analysis, and implementation support, which significantly widens the trigger surface.

Vague Triggers

High

• Confidence: 96% confidence
• Finding: The trigger guidance includes broad, common words such as security, gate, every, and practical workflow, which can cause the skill to activate in many unrelated conversations. Over-broad activation creates confused-deputy risk: the agent may invoke this skill unexpectedly, exposing internal workflow behavior, displacing more appropriate safeguards, or steering tasks into an unintended security-analysis path.

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: The trigger sentence is still overly generic and lacks clear conditions for when the skill should or should not run. This increases accidental invocation probability, which can degrade routing accuracy, produce irrelevant outputs, and in security-sensitive contexts may cause the wrong helper workflow to engage before the user has clearly requested it.

VirusTotal

64/64 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.