Product Validation Planner

• Outcome: Pass
• Latest audit: Jun 20, 2026 at 3:31 PM UTC
• Version:
  0.1.0

Overview

This is a text-only product-planning skill with broad activation wording but no hidden access, executable code, credential use, or destructive behavior.

Install only if you want product validation planning assistance. Because implicit invocation is enabled with broad product and startup keywords, explicitly name the skill when you want it and ignore or disable it if it appears in unrelated business-planning conversations.

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: 89% confidence
• Finding: The trigger phrase is broad enough to match common product-help requests, which can cause the skill to activate outside narrowly intended scenarios. In an agent system, overbroad activation can steer users into this workflow when a different skill or more neutral handling would be more appropriate, increasing the risk of misrouting and unintended instruction influence.

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: The activation guidance lists broad keywords and generic trigger sentences but does not define clear constraints, exclusions, or required intent signals. This makes accidental or excessive activation more likely, which is dangerous because the skill can capture ordinary user requests and bias the agent toward a prepackaged planning workflow without sufficient user intent confirmation.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The trigger phrases are broad enough to match many ordinary product, startup, and workflow requests, which can cause this skill to activate in situations where the user did not explicitly ask for it. Overbroad activation increases the chance of prompt-routing mistakes, unintended instruction precedence, and unnecessary exposure to any risky logic contained in the skill.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The trigger keywords are very broad and map to common, high-frequency product discussions such as 'validation', 'prototype', 'saas', and 'startup'. This can cause the skill to activate in many unrelated contexts, increasing the chance that generic skill guidance overrides more appropriate domain-specific handling or exposes users to unintended workflows.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The manifest description says to use the skill for broad categories like 'business-and-operations', 'product idea', and 'implementation support', which are much wider than the concrete requirement the skill is meant to address. Ambiguous invocation criteria can lead to over-selection of this skill, causing irrelevant activation and reducing routing precision across the agent system.

Vague Triggers

Medium

• Confidence: 94% confidence
• Finding: The description is broadly scoped around business operations, product ideas, validation, prototypes, and SaaS, which are common topics in ordinary user conversations. This can cause the skill to activate outside its intended niche, leading to prompt injection of irrelevant instructions into unrelated tasks and reducing routing precision.

Vague Triggers

Medium

• Confidence: 96% confidence
• Finding: The trigger keywords include highly generic terms like "validation," "prototype," "saas," and "startup," which are likely to appear in many benign conversations. Overbroad keyword matching increases accidental activation risk, causing the skill's instructions to inappropriately influence unrelated sessions.

Vague Triggers

Medium

• Confidence: 86% confidence
• Finding: The default prompt embeds a very broad invocation phrase tied to common product, business, validation, prototype, and workflow requests, which increases the chance of unintended or overly frequent routing to this skill. Because implicit invocation is enabled, this broad trigger surface can cause the agent to activate in contexts the user did not clearly intend, leading to misrouting, unexpected prompt injection exposure from the skill, or inappropriate handling of unrelated requests.

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: The trigger sentence begins with a very broad everyday phrase ('Help me') and then appends the requirement text, making activation plausible in many ordinary conversations that are not actually requesting this specific skill. Over-broad triggers can cause unintended routing or invocation, which is a security and safety issue because the skill may run in contexts the user did not explicitly intend.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The trigger sentence uses ambiguous activation language ('I need a practical workflow for ...') that is broad enough to match many benign requests for planning help. In a business-and-operations skill with wide topical overlap, this increases the chance of accidental activation and misrouting, especially when users ask for generic workflows rather than explicit product-validation assistance.

VirusTotal

63/63 vendors flagged this skill as clean.