Error Message Improver

• Outcome: Pass
• Latest audit: Jul 24, 2026 · 5:44 PM UTC
• Version: 0.1.0

Overview

This is a documentation-only skill for improving error messages, with some overbroad activation wording but no hidden execution, data access, persistence, or destructive behavior.

Installers should consider narrowing the trigger text to explicit error-message improvement requests or disabling implicit invocation if accidental activation would be disruptive. From a security perspective, the reviewed files do not show hidden behavior, credential handling, persistence, or destructive actions.

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

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The trigger sentence is phrased as a broad natural-language request ('Help me...'), which increases the chance that the skill may activate during ordinary conversation rather than only when explicitly intended. In an agent ecosystem, unintended invocation can cause workflow hijacking, irrelevant responses, or prompt-routing conflicts, even if the skill itself is not overtly dangerous.

Vague Triggers

Medium

• Confidence: 87% confidence
• Finding: The invocation guidance is not tightly constrained and lists generic keywords like 'debugging,' 'support,' and 'user feedback,' which overlap with many unrelated requests. This broad matching surface can cause accidental routing to the skill, reducing predictability and potentially interfering with safer or more appropriate tools.

Vague Triggers

Medium

• Confidence: 95% confidence
• Finding: The trigger phrases are very generic (e.g. help me, I need a practical workflow, use the skill to handle) and overlap with common support, debugging, and productivity requests. In an agent skill-routing system, this can cause the skill to activate unintentionally, hijacking unrelated conversations and steering users into a workflow they did not explicitly request.

Vague Triggers

High

• Confidence: 92% confidence
• Finding: The skill description is broad enough to match many common support and productivity requests, which can cause the skill to be invoked outside its intended scope. Over-broad auto-invocation can steer unrelated conversations into this workflow, leading to incorrect assistance, prompt-surface expansion, and interference with more appropriate skills.

Vague Triggers

High

• Confidence: 96% confidence
• Finding: The trigger keywords are highly generic terms like 'debugging', 'support', and 'user feedback', which are common across many unrelated requests. This raises the chance of unintended invocation, causing the agent to select this skill in situations where it is not relevant and potentially degrading routing accuracy or exposing the system to unnecessary instruction overlap.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The activation description is overly broad and ties the skill to generic categories like productivity, debugging, support, and implementation help without clear boundaries or exclusions. This can cause the skill to trigger in many unrelated contexts, leading to unintended routing, confused delegation, and possible overshadowing of more appropriate specialized skills.

Vague Triggers

Medium

• Confidence: 95% confidence
• Finding: The keyword list uses highly generic terms such as 'debugging', 'support', and 'user feedback' without qualifiers, making accidental activation likely. In a skill-routing environment, this broad matching can divert requests away from safer or more relevant skills, degrading reliability and potentially exposing users to incomplete or incorrect assistance.

Vague Triggers

Medium

• Confidence: 87% confidence
• Finding: The default invocation prompt uses broad, everyday-language phrasing such as helping with productivity, debugging, support, and implementation support. This can cause the skill to activate in many loosely related conversations, increasing the chance of unintended routing, prompt-scope confusion, or the skill influencing tasks outside its narrowly intended purpose.

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: Implicit invocation is enabled without any visible activation guardrails, allowing the system to invoke this skill automatically based on broad contextual matches. In combination with the generic prompt wording, this increases the risk of over-invocation, unintended handling of user requests, and inappropriate exposure of the skill's behavior in contexts where it was not specifically requested.

Vague Triggers

High

• Confidence: 94% confidence
• Finding: The trigger phrase is broad enough to match ordinary user language such as generic requests for help, practical workflows, or support. In an agent-routing system, this can cause unintended activation of the skill outside its intended scope, leading to prompt hijacking of workflow selection, incorrect delegation, or leakage of user context into the wrong processing path.

Vague Triggers

Medium

• Confidence: 91% confidence
• Finding: The trigger sentence is insufficiently scoped because it invokes the skill based on a vague request pattern rather than a precise task boundary. Ambiguous activation criteria increase the chance of misrouting benign conversations into this skill, which can distort outputs, override more appropriate skills, and reduce trust in the system's control-plane behavior.

VirusTotal

63/63 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.