Security audit

Product Opportunity Research

Security checks for vulnerabilities and agentic risk

Overview

This is a disclosed Markdown-only product research workflow skill with no executable code, persistence, credential handling, or hidden data movement.

Install this if you want a Chinese-language, structured product opportunity research workflow. Review the broad activation terms if you do many generic market or strategy tasks, and expect to confirm the research scope before the deeper multi-agent analysis begins.

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
Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
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 (5)

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The trigger list contains very broad phrases such as product research, market analysis, product strategy, and deep research, which can cause the skill to activate for many generic business or research requests outside its intended niche. Over-broad activation can route unrelated prompts into a heavyweight multi-agent workflow, increasing the chance of inappropriate scope capture, misleading outputs, or unintended handling of sensitive strategic or compliance topics without explicit user intent.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The title and all instructional content are written in Chinese, which effectively imposes a specific language for using this protocol. The file does not mention any user language choice, opt-in, or region-specific justification, so it appears to violate the language/locale policy criterion.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The template hard-requires Chinese-only output regardless of user preference or task context. This can override the user's requested language, reduce transparency for non-Chinese-speaking reviewers, and create a policy-compliance issue in multi-locale environments where outputs must match user locale or accessibility requirements.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 89% confidence
Finding: 文件标题及核心指令均以中文固定表述，并在 L03 以“必须”规定执行方式，但没有说明这是面向中文用户的特定场景，也没有给出语言/locale 选择。这属于自然语言层面的语言策略约束，可能与要求提供语言选择或用户 opt-in 的组织政策冲突。
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The entire skill document is written only in Chinese and provides no indication that users may choose another language or locale. Under the policy rule for natural-language violations, a skill that effectively requires one language without opt-in should be flagged unless the locale restriction is explicitly justified.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.