Security audit

Product Validation Planner

Security checks across malware telemetry and agentic risk

Overview

This is a product-validation planning workflow with no hidden execution behavior; its main caveat is broad automatic invocation wording.

Install this if you want product idea validation workflows and planning templates. Be aware it may activate for broad business, startup, prototype, or validation prompts, so review outputs for fit if you intended a different kind of business or technical help.

SkillSpector

By NVIDIA

Vulnerability Patterns

Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
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 (12)

Vague Triggers

Medium

Confidence: 89% confidence
Finding: The trigger sentence is extremely broad and can match ordinary user requests about help, workflows, or product ideas without strong constraints. That increases the chance the skill is invoked when it is not the best fit, causing scope confusion, unintended routing, and possible overshadowing of more appropriate skills or system behavior.

Vague Triggers

Medium

Confidence: 92% confidence
Finding: The invocation guidance lacks precise boundaries and relies on generic keywords like 'validation', 'prototype', and 'startup', which are common across many unrelated requests. In an agent environment, this can lead to over-invocation, accidental context capture, and reduced reliability of skill selection.

Vague Triggers

Medium

Confidence: 90% confidence
Finding: The trigger phrases are broad enough to match common business/product requests and one example explicitly invokes the skill by name, increasing the chance of accidental or over-eager activation outside the user's actual intent. In an agent system, ambiguous activation can route unrelated conversations into this workflow, causing context hijacking, user confusion, or inappropriate task execution rather than direct code-execution harm.

Vague Triggers

High

Confidence: 95% confidence
Finding: The skill description is scoped to very broad categories like business, product idea, prototype, and implementation support, which can cause the skill to activate for many loosely related requests. Overbroad routing increases the chance of inappropriate invocation, causing the agent to follow this skill's workflow when a more suitable or safer skill should handle the request.

Vague Triggers

High

Confidence: 97% confidence
Finding: The trigger keywords are generic terms like validation, prototype, saas, and startup, and the example trigger phrases are similarly broad. This makes accidental or excessive matching likely, which can misroute user requests and expand the skill's influence beyond its intended domain.

Natural-Language Policy Violations

Medium

Confidence: 88% confidence
Finding: The workflow directs the agent to prefer local-hardware-friendly approaches by default, imposing a technical preference without confirming the user's environment or priorities. While not overtly dangerous, it can bias recommendations away from better-fitting hosted or cloud options and produce suboptimal guidance for the user's actual constraints.

Vague Triggers

Medium

Confidence: 94% confidence
Finding: The skill description and usage criteria are broad enough to match common product and business queries, which can cause the skill to activate outside its intended scope. Over-broad invocation increases the chance of prompt hijacking between skills, irrelevant tool use, or unintended disclosure of context to a skill that was not specifically needed.

Vague Triggers

Medium

Confidence: 96% confidence
Finding: The trigger section lists only generic keywords such as business-and-operations, product idea, validation, prototype, saas, and startup, without disambiguation or negative controls. Because these phrases are frequent in normal conversation, the skill may be invoked accidentally, causing incorrect routing and unnecessary exposure of user context to this skill's instructions.

Vague Triggers

Medium

Confidence: 93% confidence
Finding: The skill enables implicit invocation with no narrowly defined activation condition, which can cause it to trigger on broad, ordinary user requests. Because this skill covers business, product ideas, workflows, and implementation support, unintended routing is plausible and may expose users to unrequested influence or actions from the skill in contexts where it was not explicitly chosen.

Vague Triggers

Medium

Confidence: 90% confidence
Finding: The default prompt uses very broad business-language phrasing such as helping with founders, builders, product ideas, validation, prototypes, and implementation support. This overlaps with many common requests, increasing the chance that the skill is auto-selected or suggested outside its intended boundary, especially when combined with implicit invocation.

Vague Triggers

High

Confidence: 89% confidence
Finding: The trigger sentence is overly broad and generic enough that the skill may activate for routine requests that are only loosely related to product validation. That can cause inappropriate routing, unexpected use of this skill, and make prompt-injection or instruction-shadowing issues more reachable because the skill is invoked in more contexts than intended.

Vague Triggers

Medium

Confidence: 92% confidence
Finding: The invocation guidance defines broad keywords and example triggers without firm boundaries, so the skill can be selected for many ordinary business, product, or startup prompts that do not actually require this workflow. In a skill-routing system, ambiguous scope increases the chance of misrouting, policy bypass through over-invocation, and user confusion about why this capability was applied.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.