Security audit

Product Validation Planner

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only product validation helper with broad auto-invocation wording but no evidence of hidden execution, data theft, persistence, or privilege misuse.

This skill is reasonable to install for product idea validation work. Be aware that it may activate on broad startup, SaaS, prototype, or business prompts; use explicit prompts or disable implicit invocation if you want tighter routing. Share only the business context needed for the validation task.

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: 92% confidence
Finding: The invocation guidance defines broad keywords and trigger patterns without clear exclusion criteria, making the skill eligible for a wide range of common startup, SaaS, and operations requests. In a multi-skill agent environment, this can lead to misrouting and unintentional invocation, which is a security and reliability concern because the skill gains influence over conversations it was not specifically selected to handle.
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 generic help-seeking language that could cause the skill to activate for many ordinary product or business queries beyond its intended scope. Overbroad activation can hijack routing, suppress more appropriate skills, and increase the chance that users receive irrelevant or lower-quality guidance without explicit consent.
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 generic and map to broad, common user intents such as 'validation', 'prototype', 'saas', and 'startup', which can cause the skill to activate outside its intended scope. Over-broad activation boundaries increase the chance of prompt/skill routing conflicts, unintended invocation, and the skill influencing requests it was not specifically selected for.
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 many ordinary business, product, and implementation requests, which increases the chance of unintended invocation. Over-broad routing can cause the agent to apply this skill in situations it was not designed for, leading to irrelevant guidance, scope confusion, or bypass of more appropriate specialized skills.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The trigger keywords are highly generic terms like 'validation', 'prototype', 'saas', and 'startup', which commonly appear in many unrelated requests. Ambiguous triggers make accidental or excessive invocation more likely, reducing routing precision and potentially steering users into an ill-fitting workflow.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The skill description and activation scope are broad enough to match many ordinary business, product, or SaaS-related requests, which can cause unintended invocation. Over-broad routing is dangerous because it increases the chance that the agent applies this skill in contexts where it is only partially relevant, leading to incorrect assumptions, scope hijacking, or bypass of more appropriate specialized skills.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The keyword trigger list relies on very generic terms without contextual constraints, making accidental activation likely during routine conversations about startups or products. This creates a routing vulnerability: the skill may intercept unrelated requests and steer execution toward its own workflow, reducing reliability and potentially exposing users to irrelevant or misleading outputs.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 92% confidence
Finding: The example trigger phrases are written as broad everyday requests, which can collide with normal user language and train the router toward over-activation. In context, this skill is operational rather than privileged, so the impact is not direct code execution, but it still meaningfully increases misrouting risk and can degrade safety and task correctness across adjacent business-support 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 extremely broad and generic, encouraging invocation for a wide range of business, product, validation, prototype, and implementation-related requests without clear task boundaries or safety constraints. In practice, this increases the chance of over-triggering the skill in contexts where it may receive sensitive business data or be applied outside its intended scope, creating prompt-routing and least-privilege issues.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 91% confidence
Finding: Enabling implicit invocation without a tightly defined trigger scope allows the system to auto-select this skill for loosely related user requests. Because the skill targets broad founder and builder workflows, it may be invoked on ambiguous prompts and gain access to conversations or context it does not need, increasing the risk of inappropriate action selection and exposure of sensitive planning or operational information.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The trigger sentence begins with a highly generic phrase ('Help me ...'), which can cause the skill to activate on many unrelated user requests. Over-broad activation increases the chance that this skill intercepts prompts outside its intended scope, leading to misrouting, prompt confusion, or accidental invocation in contexts where its business-validation workflow is inappropriate.
Content: No source excerpt is available for this finding.