Back to skill

Security audit

Idea to Product

Security checks for vulnerabilities and agentic risk

Overview

This skill is a markdown-only product-planning workflow with no executable code, persistence, credential use, or hidden high-impact behavior.

Install this if you want structured product-planning prompts. Review generated backlog, UX, and test-check outputs before applying them to project files, because the skill can influence planning direction even though it does not execute code or access sensitive data.

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The 'When to use it' section describes general situations like 'shrink a big idea' and 'design pages by relationship first' but does not define specific activation phrases, boundaries, or negative examples. In a markdown skill description, this can make invocation conditions overly broad and increase the chance of unintended matching to ordinary product-planning requests.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

This markdown file names the skill and describes its purpose, but it does not specify concrete activation phrases, scope limits, or exclusion conditions. Phrases like "/playwright-checks-to-feedback" and "Route failed checks into the right layer" are not enough to clarify when the skill should or should not be invoked, which could lead to unintended routing in loosely matched systems.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

This markdown file says the skill will 'Turn UX flow into atomic browser checks' / 'Turn UX flow into atomic Playwright checks' but does not specify when the skill should activate, what exact inputs qualify as a UX flow, or any exclusion conditions. That ambiguity could cause unintended invocation because the description is generic and lacks explicit trigger scope or negative examples.

Content

No source excerpt is available for this finding.