Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation-only product validation planning skill with broad auto-invocation metadata but no evidence of hidden code, data access, persistence, or destructive behavior.
Before installing, consider narrowing the activation wording or disabling implicit invocation if you want this skill to run only when explicitly requested for product validation planning. No dangerous runtime behavior was found in the reviewed package.
The invocation guidance lacks precise activation boundaries and exclusions, so the skill may be selected for a wide range of adjacent product, startup, or operations requests. In multi-skill environments, ambiguous routing guidance can lead to incorrect tool/skill selection, irrelevant outputs, and possible interference with safer or more appropriate skills.
The trigger sentence is framed as a very general help request and includes broad business/product wording that could overlap with many ordinary user prompts. In agent systems that auto-select skills based on loose semantic matching, this increases the chance of unintended invocation, causing the planner to activate in contexts where the user did not explicitly request it.
The trigger phrases are broad and map to common, natural user requests such as needing a practical workflow or help with product ideas. This can cause the skill to activate in situations beyond the author's intended scope, increasing the chance of inappropriate routing, unexpected behavior, or the skill overshadowing more suitable tools.
The skill description and use conditions are broad enough to match many ordinary product, startup, and planning requests, which can cause the agent to invoke this skill when it was not specifically intended. Over-broad activation increases the chance of misrouting user queries, overshadowing more appropriate skills, and expanding the effective instruction surface exposed to untrusted skill content.
The listed keywords are highly generic business terms that appear frequently in normal conversation, making unintended activation likely. In an agent environment, this can route broad classes of unrelated requests through this skill, potentially degrading behavior, causing instruction conflicts, or exposing users to irrelevant or lower-priority guidance.
The front-matter description says to use the skill whenever users ask about broad categories like business operations, product ideas, validation, prototypes, or SaaS, without clear limiting conditions. This makes accidental invocation likely and can misdirect unrelated requests into this skill's workflow, reducing routing integrity and creating opportunities for unintended behavior.
The skill file is written entirely in Simplified Chinese and presents its workflow, expected output, and trigger guidance only in that language, without stating that language selection is optional or user-driven. This can violate language or locale policy if the skill is applied to users who did not opt into Chinese output.
The trigger keywords and example invocations are broad enough to match many ordinary startup, product, and business conversations, which can cause the skill to activate outside its intended scope. Over-broad activation can route users into an unintended workflow, override better-matched skills, and increase exposure to prompt-scope abuse or irrelevant guidance.
The default prompt is broad and effectively encourages invocation for a wide range of loosely related requests without clear boundaries. In an agent-routing system, this can cause the skill to be selected in contexts the user did not intend, increasing the chance of over-collection of context, unintended actions, or interference with more appropriate skills.
Enabling implicit invocation without narrowing conditions allows the platform to auto-select this skill based on vague semantic overlap rather than clear user intent. Because this skill targets broad business-and-operations and implementation support use cases, the lack of guardrails increases the risk of accidental activation and inappropriate handling of unrelated user tasks.
The trigger sentence is overly broad and resembles ordinary user phrasing, which can cause the skill to activate for loosely related requests rather than explicit intent to use this business-planning workflow. This increases the chance of inappropriate routing, unexpected prompt injection exposure from unrelated contexts, and degraded safety controls because the skill may handle requests outside its intended scope.
This file is a Chinese-language README and does not indicate that users may choose another language or locale for interaction. Under the policy, forcing a specific language without opt-in can be a natural-language policy concern unless the locale restriction is explicitly justified.
No suspicious patterns detected.
