Security audit
Security checks for vulnerabilities and agentic risk
This skill is a documentation helper that turns Chinese-language demo or requirement descriptions into technical planning documents, with no executable code or hidden system access found.
Install this if you want a Chinese-language workflow for converting demos or requirements into technical planning documents. Review outputs carefully because the skill is designed to infer fields, APIs, data ownership, and tasks from incomplete inputs, although it requires those inferences to be marked for confirmation.
The entire skill description and invocation prompt are written only in Chinese, and the quick-start prompt instructs a fixed response style without offering the user a language or locale option. Under the stated policy, forcing a specific language without opt-in is a natural-language policy violation unless the locale constraint is explicitly documented and justified.
The trigger phrases are broad enough to match common documentation and product-planning requests, which can cause the skill to activate outside its intended scope. This increases the chance of context hijacking or accidental routing of unrelated user tasks into a rigid workflow that infers requirements, interfaces, and data structures from incomplete inputs.
This markdown template is entirely written in Chinese and provides no indication that language selection is optional or that the template is specifically intended for a Chinese-language or region-specific context. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation.
This JSON template includes natural-language values in Chinese (for example, the source field options) while providing no indication that the skill is intended only for Chinese-speaking users or that language selection is configurable. That can violate a language/locale policy requiring user choice or explicit justification for a fixed locale.
The status field uses Chinese-only options, which forces a specific language in the template output. Because the file does not document a region-specific scope or offer user language choice, this is a natural-language policy concern.
Fields such as level, owner, and type define Chinese-only allowed values across the template. In the absence of explicit locale justification or opt-in, the template effectively mandates one language, which may conflict with organizational language-choice policy.
No suspicious patterns detected.
