Security audit

Product Validation Planner

Security checks for vulnerabilities and agentic risk

Overview

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

Installers should be aware that this skill may activate on general product, startup, validation, or SaaS requests. Review whether that broad routing is acceptable for your environment, but the artifact itself is limited to advisory planning content.

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

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

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The trigger phrases are generic and map to common product/business language such as 'validation,' 'prototype,' and 'practical workflow,' which increases the likelihood that the skill is invoked when a user did not specifically intend to use it. Unintended invocation can route conversations into the wrong workflow, causing inappropriate handling of user requests and reducing trust in agent behavior; while not code-execution dangerous, it is a real security/quality boundary issue for skill selection.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The trigger phrases are broad enough to activate on common business, startup, validation, or prototype-related requests without clear scoping constraints. In an agent ecosystem, this can cause unintended invocation, context hijacking, or routing of users into a workflow they did not explicitly request, which is a genuine security and safety concern even though the file itself does not contain direct code execution behavior.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 94% confidence
Finding: The skill description is written broadly enough that it can match many ordinary product, startup, planning, and operational requests, which increases the chance of unintended invocation. Over-broad routing can cause the agent to select this skill in contexts where it is not the best fit, leading to irrelevant guidance, prompt-surface expansion, and possible interference with more appropriate or safer skills.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The keyword list uses highly generic terms such as product idea, validation, prototype, saas, and startup, which are common across many benign user requests and many other skills. This makes accidental triggering likely and can route unrelated conversations into this skill, increasing misapplication risk and reducing control over which instructions are applied.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 90% confidence
Finding: The invocation description says to use the skill whenever users ask for broad categories like business operations, product ideas, validation, prototypes, or SaaS support, without clearly delimiting when it should not be used. This ambiguity can lead to excessive or unintended invocation, which may override more appropriate skills or steer conversations into a fixed workflow not relevant to the user's request.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The trigger keywords are broad generic business/product terms such as 'validation', 'prototype', and 'startup', which can cause the skill to activate for many ordinary requests outside its intended scope. Over-broad activation increases the chance of prompt routing errors, causing irrelevant instructions to be injected into unrelated conversations and potentially degrading safety or correctness.
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 framed so broadly that the skill can be invoked for a wide range of loosely related business, product, validation, prototype, and implementation requests without clear boundaries. In combination with implicit invocation, this increases the chance of unintended routing, prompt hijacking through ambiguous user intent, or the skill being applied in contexts where its behavior was not expected or appropriately constrained.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The activation examples are ambiguous and underspecified, because they embed a long requirement description instead of realistic, bounded user intents. This can make matching unreliable and overinclusive, causing accidental activation on generic business, operations, or workflow requests that only partially resemble the requirement.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The trigger examples use broad natural-language phrases like 'Help me' and 'I need a practical workflow' tied to a very wide business topic, which can cause the skill to activate for loosely related requests. Over-broad activation increases the chance of unintended invocation, where the agent may apply this planning workflow in contexts the user did not explicitly request, reducing predictability and weakening routing safety boundaries.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 86% confidence
Finding: This README is written as a Chinese-language variant, but there is no natural-language notice in the file that clarifies it is optional, user-selected, or region-specific. Because policy violations include forcing a specific language without opt-in, the absence of an explicit language choice statement may create a locale-policy concern.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 82% confidence
Finding: The skill file is presented entirely in Simplified Chinese and does not mention that users may choose another language or locale. Because the instructions and expected outputs are language-bound, this can create a locale-policy issue if applied to users without explicit opt-in.
Content: No source excerpt is available for this finding.