Security audit

Product Validation Planner

Security checks for vulnerabilities and agentic risk

Overview

This skill is a documentation-only product validation helper with broad activation wording but no hidden code, persistence, credential access, or destructive behavior.

Install this as a low-risk planning aid, but expect it may activate in broad product, startup, or SaaS discussions because its trigger language is loose. Treat its demand evidence as background context rather than proof of market demand, and make business decisions using your own validation data.

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

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 89% confidence
Finding: The usage section relies on ambiguous natural-language examples instead of a narrowly defined activation scope, making the skill eligible for invocation across a wide range of ordinary business conversations. In agent environments, this can lead to misrouting or over-invocation, which weakens control boundaries and can be abused to steer the system into using this skill when a more appropriate or safer one should handle the request.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 94% confidence
Finding: The trigger sentence is broad and conversational enough that it could cause the skill to activate on loosely related user requests rather than explicit product-validation tasks. Over-broad activation increases the chance of unintended routing, which can expose users to irrelevant business guidance, reduce predictability, and make prompt-selection behavior easier to manipulate.
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 match many ordinary user requests about workflows, product ideas, validation, or SaaS, which can cause the skill to activate outside its intended scope. Over-broad activation increases the chance of prompt hijacking through unintended invocation and may override more appropriate skills or baseline handling.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The skill description is broad enough to match many ordinary business, product, and workflow requests, which can cause the skill to activate outside its intended niche. Over-broad routing increases the chance that this skill will intercept unrelated prompts, override more appropriate specialized skills, or produce misleading business guidance in contexts it was not designed for.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The trigger keywords are highly generic terms like 'validation', 'prototype', 'saas', and 'startup', which are common across many unrelated requests. This ambiguity can cause accidental invocation and skill-selection collisions, making agent behavior less predictable and potentially steering users into an unintended workflow.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 91% confidence
Finding: The description says the skill should be used for a wide range of requests, including broad business and product topics, without clear boundaries on when not to use it. This can lead to over-selection of the skill and unreliable task handling, especially when other specialized skills would be more appropriate.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The trigger keywords are very broad and generic, which can cause the skill to activate in many unrelated contexts. Over-broad activation increases the chance of incorrect routing, irrelevant instructions, and accidental interference with other skills or user intents.
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 broad and generic enough to match common product, business, and planning requests, which can cause the skill to be invoked in situations the user did not clearly intend. Because implicit invocation is enabled, this increases the chance of overreach, prompt steering, or unintended use of the skill's behaviors in unrelated conversations.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The trigger sentence begins with a very broad natural-language pattern ('Help me ...') that can match many ordinary user requests unrelated to this specific skill. Overbroad activation increases the chance the agent invokes the skill in unintended contexts, which can cause prompt-routing errors, irrelevant guidance, and possible interference with safer or more appropriate skills.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 91% confidence
Finding: The invocation guidance uses generic phrasing like 'I need a practical workflow for ...' and an explicit tool-call pattern without meaningful constraints, making activation too permissive. In an agentic system, this can cause accidental or adversarial skill selection by matching commonplace wording rather than a clearly delimited business-validation use case.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 86% confidence
Finding: The file labels itself as the Chinese user guide and points to separate English and Chinese documents, but within this README there is no indication that language selection is optional or user-driven. For natural-language policy review, this can be interpreted as a locale-specific presentation without explicit opt-in in the file itself.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 77% confidence
Finding: The skill content is written as a Chinese-localized variant and presents its operating instructions entirely in Chinese, but it does not state that language is optional or user-selectable. Under the stated policy, forcing a specific language without opt-in can be a natural-language policy violation unless the locale constraint is documented and justified.
Content: No source excerpt is available for this finding.