Back to skill

Security audit

Product Validation Planner

Security checks for vulnerabilities and agentic risk

Overview

The scanners rate this skill benign with high confidence: their results show no executable files and one concern about broad activation wording, which does not change the overall verdict.

The verdict is benign, but benign does not mean risk-free. Consider whether broad activation on terms like “validation” or “prototype” fits your use; the scan reports complete coverage of six components.

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

Activation keywords include broad terms without product-planning scope constraints.

Medium
Category
Trigger Abuse
Confidence
90% confidence
Finding

The usage section lists generic keywords such as validation and prototype without specifying whether they must occur in a product-demand planning request. These terms also apply to unrelated tasks, such as form validation or programming prototypes, and the more specific trigger sentences do not explicitly exclude those contexts.

Content

No source excerpt is available for this finding.

Activation keywords such as `validation`, `prototype`, `saas`, and `startup` are not restricted to product-demand validation requests.

Low
Category
Trigger Abuse
Confidence
88% confidence
Finding

These standalone keywords cover many requests outside this skill's purpose, such as form validation, prototype implementation, or SaaS troubleshooting. The usage section does not require a product-validation intent alongside these keywords, leaving activation scope ambiguous despite the more specific example trigger sentences below.

Content

No source excerpt is available for this finding.

Activation criteria extend beyond product-demand validation to generic workflow requests and ambiguous keywords.

Low
Category
Trigger Abuse
Confidence
96% confidence
Finding

The description activates the skill for requests about broad topics such as business-and-operations or a practical workflow, while L44 separately lists ambiguous keywords such as validation and prototype. These conditions can match unrelated tasks such as software input validation or engineering prototypes, and no explicit exclusions constrain activation to product-demand validation.

Content

No source excerpt is available for this finding.

Standalone triggers such as “validation” and “prototype” are too broad for a product-validation planning skill.

Low
Category
Trigger Abuse
Confidence
96% confidence
Finding

These keywords also occur in unrelated requests, such as input validation or prototype-based programming. The activation description on L04 treats mentioning these terms as sufficient, without requiring a product-demand validation context or providing exclusions.

Content

No source excerpt is available for this finding.