Security audit

Product Validation Planner

Security checks for vulnerabilities and agentic risk

Overview

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

Installers should expect this skill to influence product validation and startup planning conversations, and may want to narrow its trigger phrases if they only want it invoked for explicit idea-validation or MVP-planning requests.

A.I.G

Vulnerability Patterns

Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

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

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The trigger phrases are broad, natural-language requests like 'Help me' and 'I need a practical workflow', which can cause the skill to activate for generic business or planning conversations far beyond its intended scope. Over-broad activation increases the chance of unintended instruction injection into unrelated user tasks, producing confusing, inappropriate, or policy-bypassing behavior through skill overreach rather than direct code execution.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The trigger phrases are broad and partly composed of common request patterns such as 'Help me' and 'I need a practical workflow', which can cause the skill to activate in situations beyond its intended scope. Over-broad invocation increases the chance of unintended routing, prompt hijacking through ambiguous matching, or inappropriate application of the skill to unrelated user requests.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The invocation description uses expansive language like 'use when a user asks for business-and-operations, product idea, validation, prototype, saas' without clear decision boundaries. This ambiguity can cause over-invocation across a wide range of normal conversations, reducing routing precision and potentially exposing users to irrelevant or lower-quality guidance.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The trigger keywords and example phrases are broad enough to match many ordinary product or startup discussions, which can cause the skill to activate outside its intended scope. Over-broad activation increases the chance of prompt-routing errors, where this skill preempts more appropriate skills and influences outputs in situations it was not designed to handle.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The skill description is broad enough to match a wide range of normal business, product, and startup requests, which can cause unintended activation. Over-broad routing is dangerous because it may override a more appropriate skill, produce off-target guidance, and increase the attack surface for prompt/skill injection through accidental invocation.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The trigger keywords include generic terms such as business-and-operations, product idea, validation, prototype, saas, and startup, which are likely to collide with everyday conversations. This creates a real routing vulnerability because the skill can be invoked in contexts where it was not intended, leading to irrelevant actions, confusion, or inappropriate handling of user requests.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The default prompt is broadly worded and can cause the skill to be invoked for a wide range of loosely related user requests without clear boundaries. This increases the chance of unintended routing, over-collection of user context, or the skill influencing tasks outside its intended scope, especially because implicit invocation is enabled.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The invocation guidance provides keywords and trigger phrases but does not define boundaries, prerequisites, or when the skill should not be used. This ambiguity can lead to skill overreach, where the agent invokes this planner for general startup, SaaS, or prototype questions outside its intended scope, reducing reliability and potentially exposing users to mismatched guidance.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The trigger sentence is extremely broad and can match ordinary product, business, or planning requests that are not specifically about this skill’s validated workflow. Over-broad triggers increase the chance of unintended invocation, causing the agent to apply the wrong capability, collect unnecessary context, or bypass more appropriate specialized skills.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 79% confidence
Finding: In a file labeled as Simplified Chinese, key user-facing description and trigger phrases are presented in English only. This can amount to an implicit language constraint for users of the zh-CN variant without any opt-in or explanation.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 88% confidence
Finding: The skill file presents the operational instructions and usage guidance entirely in Chinese, with no statement that the user can choose another language. This can violate language-choice policy when the skill is applied to users who did not opt into Chinese output.
Content: No source excerpt is available for this finding.