Error Message Improver

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

Overview

This is a documentation-only skill for improving error messages, with broad activation wording but no hidden execution, data access, persistence, or credential handling.

Before installing, be aware that this skill may be invoked for some general debugging or support requests because its triggers are broad. It appears safe as a markdown-only helper, but users who want precise routing should narrow activation to explicit error-message improvement tasks.

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

Medium

• Confidence: 91% confidence
• Finding: The trigger sentence is so broad and awkwardly phrased that it can match ordinary user requests about help, support, or workflows, causing the skill to activate outside a clearly intended scope. Over-broad activation increases the chance of unintended instruction injection into unrelated conversations and can interfere with safer or more appropriate skills.

Vague Triggers

Medium

• Confidence: 94% confidence
• Finding: The invocation guidance relies on ambiguous natural-language examples instead of precise activation rules, which can cause accidental triggering during normal conversation. In an agent environment, this broad matching can misroute user requests, apply the wrong workflow, or let untrusted content influence behavior when the user did not intentionally invoke the skill.

Vague Triggers

Medium

• Confidence: 88% confidence
• Finding: The trigger phrases are very broad and map to common, everyday support or productivity requests, which can cause the skill to activate outside its intended scope. Overbroad invocation increases the chance of unintended routing, prompt collisions with other skills, and user confusion about why this skill was selected.

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: The skill description is broad enough to match common support, productivity, and debugging requests without strong boundaries, which can cause the agent to invoke this skill in situations outside its intended scope. Over-broad routing increases the chance of misapplication, unintended disclosure of user context to the wrong skill path, or degraded security review because the skill becomes a generic catch-all.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The trigger list uses generic terms like 'debugging', 'support', and 'user feedback' that appear in many unrelated requests, making accidental or excessive invocation likely. In practice, broad trigger terms can let this skill intercept requests it was not designed to handle, reducing routing precision and potentially exposing sensitive troubleshooting content to an unnecessary processing path.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The trigger keywords are very broad and overlap with common support and productivity conversations such as 'debugging', 'support', and 'user feedback'. This can cause the skill to activate in many unrelated contexts, leading to prompt routing confusion, unintended instruction injection into normal chats, or the wrong workflow being applied without user intent.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The description defines an overly broad usage scope covering multiple generic domains without clear exclusion criteria. In a skill-routing system, this increases the chance of accidental invocation on ordinary work-productivity or support requests, which can mis-handle user input and expand the attack surface for prompt misrouting or unintended tool behavior.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The default prompt is broad and closely matches ordinary user requests about error messages, which can cause this skill to be invoked in situations where the user did not explicitly intend to call it. Combined with allow_implicit_invocation: true, this increases the chance of over-triggering, prompt-routing confusion, and unintended exposure of user context to the skill.

Vague Triggers

High

• Confidence: 90% confidence
• Finding: The trigger sentence is phrased in broad, natural language that overlaps with ordinary user requests, which can cause the skill to activate when the user did not explicitly intend to invoke it. Unintended invocation can route conversations into the wrong workflow, increase prompt-scope confusion, and create opportunities for instruction hijacking or misuse of the skill in contexts where it is not appropriate.

Vague Triggers

Medium

• Confidence: 94% confidence
• Finding: The usage-signal section defines activation criteria so loosely that many unrelated debugging, support, or productivity prompts could match. In an agentic environment, ambiguous routing increases the chance of unintended skill execution, which can override more suitable skills, mishandle user intent, or expose the system to broader prompt-injection surface through unnecessary skill loading.

VirusTotal

64/64 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.