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 evidence of code execution, data access, persistence, or deception.

Install only if you want product-validation planning help. Be aware it may activate for broad startup, SaaS, prototype, or validation wording, so invoke a different skill explicitly when you need unrelated business advice.

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

Vague Triggers

High

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The description includes very broad routing cues such as 'business-and-operations,' 'product idea,' 'validation,' 'prototype,' and 'implementation support,' which can match many ordinary requests outside the skill's intended niche. Over-broad activation increases the chance this skill is invoked inappropriately, causing misrouting, irrelevant guidance, or unintended overshadowing of more suitable skills.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The trigger keywords and example sentences are generic enough to fire on common startup, product, or business queries without confirming that the user actually needs a structured product-validation workflow. This makes accidental invocation likely and can degrade system behavior by routing broad categories of requests into a narrowly intended skill.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The trigger sentence is so broad and unnatural that it can match loosely phrased user requests about product help, validation, or workflows without clear boundaries. This increases the chance the skill is invoked outside its intended scope, causing prompt-routing confusion and potentially exposing users to irrelevant or lower-quality business guidance when another skill would be more appropriate.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The trigger phrases are broad and map to common business/product requests, which increases the chance the skill activates in situations where the user did not explicitly intend to invoke it. In an agent ecosystem, ambiguous activation can cause misrouting, unintended instruction precedence, or over-application of this skill's workflow to unrelated tasks.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The trigger phrase is broad enough to match routine help requests about workflows or product ideas, which can cause the skill to activate outside its intended scope. In an agent system, overbroad invocation increases the chance of unintended routing, irrelevant instruction injection into benign conversations, and user confusion about why this skill was selected.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 94% confidence
Finding: The trigger conditions are overly broad and include generic terms like business-and-operations, validation, prototype, saas, and startup without meaningful disambiguation. This can cause the skill to activate for many unrelated requests, increasing the chance it overrides more appropriate skills, produces off-target guidance, or is invoked in contexts the author did not intend.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The default prompt uses a very broad invocation phrase tied to a wide range of business, product, and implementation requests, which increases the chance the skill is auto-invoked outside narrowly intended scenarios. Because implicit invocation is also enabled, this can cause unintended routing of user requests, over-collection of context, or inappropriate reliance on this skill in situations where a more specific or safer tool should be used.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 91% confidence
Finding: The invocation section does not define clear scope limits, exclusions, or disambiguation criteria, so the router may select this skill for general business, product, or operations queries that it is not uniquely suited to handle. Ambiguous trigger scope is dangerous because it undermines predictable skill selection and can be abused by broad matching to hijack adjacent requests.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 72% confidence
Finding: The file lists English and Chinese instruction and guide files, but does not state how the user's preferred language is selected or that language choice is optional. This can create an implicit locale behavior without explicit user opt-in.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 85% confidence
Finding: This file is labeled as a Chinese README, but key descriptive and usage content is presented in English, which can effectively impose a language choice on users without opt-in. The document does not explain that bilingual content is intentional or offer the user a clear language-selection option.
Content: No source excerpt is available for this finding.