Security audit

Product Validation Planner

Security checks across malware telemetry and agentic risk

Overview

This is a documentation-only product validation planning skill with broad activation wording but no code execution, persistence, credential access, or hidden data handling.

Before installing, be aware this skill may be invoked for broad product, startup, SaaS, or validation requests. It appears safe from a security standpoint, but users who want precise routing may prefer narrower trigger wording or explicit invocation.

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

Vague Triggers

Medium

Confidence: 91% confidence
Finding: The trigger phrases are generic and map to broad business and product terms, which increases the chance the skill is invoked for loosely related requests rather than explicit user intent. In an agent system, over-broad activation can cause prompt-routing mistakes, unexpected workflow execution, and leakage of user context into an unintended skill path.

Vague Triggers

Medium

Confidence: 94% confidence
Finding: The trigger phrases are broad and map to common requests such as needing 'a practical workflow' or help with product ideas, validation, prototypes, and SaaS. This can cause the skill to activate in many ordinary conversations where the user did not explicitly intend to invoke it, leading to over-selection, context hijacking, or inappropriate routing of user requests.

Vague Triggers

High

Confidence: 91% confidence
Finding: The skill description contains broad routing terms like "business-and-operations," "product idea," and "implementation support," which are common across many unrelated user requests. In an agentic system, this can cause the skill to be invoked outside its intended niche, leading to inappropriate behavior, lower-quality responses, or accidental overshadowing of more suitable skills.

Vague Triggers

High

Confidence: 95% confidence
Finding: The trigger keywords and example trigger phrases are highly ambiguous and generic, with no disambiguation rules or negative examples. This increases the chance of false-positive activation for ordinary startup, SaaS, prototype, or validation queries that may not actually require this specific workflow, creating routing confusion and possible instruction hijacking of adjacent domains.

Vague Triggers

Medium

Confidence: 89% confidence
Finding: The trigger keywords are very broad and overlap with common product, startup, and business discussions, which can cause the skill to activate outside its intended scope. In an agent environment, this increases the chance of inappropriate routing, irrelevant execution, or the skill influencing responses when a more suitable skill or direct answer should have been used.

Vague Triggers

Medium

Confidence: 86% confidence
Finding: The usage description says to use the skill whenever the user mentions broad domains or needs practical support, but it does not define clear inclusion and exclusion criteria. This ambiguity can lead to over-invocation across many ordinary conversations, creating misrouting risk and allowing the skill to shape outputs in cases where it is not the best or safest fit.

Vague Triggers

Medium

Confidence: 93% confidence
Finding: The skill enables implicit invocation without any visible activation constraints, which allows the agent to call it automatically based only on broad relevance matching. Because this skill deals with business planning and analysis workflows, unscoped automatic activation can cause unintended execution, prompt-surface expansion, and routing of user context into the skill when the user did not explicitly request it.

Vague Triggers

High

Confidence: 97% confidence
Finding: The trigger phrases are broad enough to match many ordinary requests about product ideas, workflows, or startup help, which can cause the skill to activate outside its intended scope. Overbroad routing is dangerous because it can hijack user intent, suppress better-matched skills, and lead to unreliable or misleading outputs in unrelated contexts.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.