Security audit

competitive analysis

Security checks for vulnerabilities and agentic risk

Overview

This is a markdown-only competitive analysis skill with templates and no hidden execution, persistence, or data access beyond user-directed research guidance.

Installers should treat this as a business analysis aid. It may prompt users to collect competitor, market, user, financial, and internal planning information, so users should avoid entering confidential business data unless they intend to use it in the analysis workflow.

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
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
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (4)

Natural-Language Policy Violations

Low

Confidence: 79% confidence
Finding: The entire template is written as fixed English headings and field labels, with no indication that users may complete or receive the canvas in another language. Under the policy rule for language/locale, this can be considered a default language constraint without explicit opt-in or documented justification.

Natural-Language Policy Violations

Low

Confidence: 93% confidence
Finding: This markdown file contains user-facing instructions exclusively in English, and it does not indicate that English is optional or required for a specific regional/compliance context. Under the policy rule for language or locale constraints, forcing a single language without user opt-in can be considered a natural-language policy issue.

Natural-Language Policy Violations

Low

Confidence: 89% confidence
Finding: This markdown template presents all user-facing instructions in English and does not mention any option to use another language or locale. Under the stated policy, forcing a specific language without user opt-in can be a natural-language policy violation.

Natural-Language Policy Violations

Low

Confidence: 88% confidence
Finding: This markdown template presents all instructions, labels, and guidance in English and does not indicate that users may choose another language or locale. Under the policy provided, forcing a specific language without user opt-in is a natural-language policy concern.

Static analysis

No suspicious patterns detected.