Security audit

Product Validation Planner

Security checks across malware telemetry and agentic risk

Overview

This skill is a disclosed product-validation planning helper with no executable code, persistence, credential use, or hidden data handling.

Before installing, be aware that this skill may activate broadly around product ideas, validation, prototypes, SaaS, or startups. It appears safe as a planning aid, but users who want tighter routing should prefer explicit invocation with $product-validation-planner.

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

Vague Triggers

Medium

Confidence: 92% confidence
Finding: The trigger phrases are broad, natural-language requests that could match many ordinary conversations about help, workflows, or product ideas without strong activation boundaries. This increases the chance of unintended skill invocation, causing the agent to steer users into this workflow when they did not explicitly request it, which can override user intent or crowd out more appropriate skills.

Vague Triggers

Medium

Confidence: 90% confidence
Finding: The trigger phrases are broad and partially generic, which raises the likelihood that the skill will be invoked when a user did not explicitly intend to use it. In an agent environment, unintended invocation can cause workflow hijacking, irrelevant task execution, or disclosure of user context to the wrong skill, especially because the skill targets common startup and product-planning queries.

Vague Triggers

Medium

Confidence: 94% confidence
Finding: The skill description is broad enough to match many ordinary requests about business, product ideas, prototypes, SaaS, workflows, and analysis. This can cause unintended activation and routing, which may override a more appropriate skill or inject irrelevant instructions into unrelated conversations, reducing safety and predictability.

Vague Triggers

Medium

Confidence: 97% confidence
Finding: The trigger keywords are highly generic and likely to appear in many benign user prompts, making accidental invocation probable. Overbroad keyword matching increases the chance that this skill captures requests outside its intended scope, leading to prompt-space contamination and misapplication of the workflow.

Vague Triggers

Low

Confidence: 90% confidence
Finding: The example trigger sentences are vague and effectively restate the broad requirement instead of defining precise invocation boundaries. This weakens operator and model understanding of when the skill should apply, increasing accidental activation and inconsistent behavior across similar prompts.

Vague Triggers

Medium

Confidence: 88% confidence
Finding: The skill description is broad enough to activate on many ordinary product or operations requests, which can cause unintended routing and overreach beyond the user's actual intent. In an agent system, ambiguous activation boundaries increase the chance that the wrong skill handles a request, leading to confusing outputs, hidden assumptions, or unsafe workflow substitution.

Vague Triggers

Medium

Confidence: 91% confidence
Finding: The keyword list is short, generic, and lacks disambiguation, so common terms such as validation, prototype, or startup may trigger the skill in unrelated contexts. This can degrade agent reliability and create prompt-routing confusion, especially when multiple skills overlap on broad business terminology.

Natural-Language Policy Violations

Medium

Confidence: 80% confidence
Finding: The body of the skill is written in Chinese without offering language negotiation or a justified locale restriction, which can cause the agent to respond in an unexpected language or misunderstand operating instructions. While this is not a direct code-execution issue, it can reduce transparency, impair user comprehension, and increase the risk of incorrect task execution.

Vague Triggers

Medium

Confidence: 88% confidence
Finding: The default prompt contains a very broad natural-language trigger phrase covering common concepts like product ideas, validation, prototypes, workflows, and implementation help. Combined with allow_implicit_invocation=true, this increases the chance the skill is invoked in ordinary conversations without clear user intent, which can cause prompt-routing confusion, unintended tool activation, or overexposure of the skill's instructions in unrelated contexts.

Vague Triggers

Medium

Confidence: 90% confidence
Finding: The trigger sentence starts with the broad phrase "Help me," which can match many ordinary user requests and cause the skill to activate outside its intended scope. In an agent system, overly generic activation patterns increase the chance of misrouting prompts, untrusted context injection, or this skill preempting more appropriate skills for unrelated tasks.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.