Security audit
Security checks for vulnerabilities and agentic risk
This is a Markdown-only Chinese technical writing guide with broad style rules but no evidence of unsafe system access or hidden behavior.
Install this if you want an opinionated Chinese technical documentation style guide. Be explicit when asking for non-Chinese, bilingual, or project-specific style so the agent does not over-apply these conventions.
The skill description enforces Chinese-only technical writing behavior based on trigger phrases, without clear opt-in or a check that the user actually wants Chinese output. If activated on ambiguous requests, it may override the user’s preferred language or writing context, leading to misaligned responses and unintended constraint application.
The trigger list includes a very broad phrase like “帮我写文档”, which can match many ordinary writing requests outside the intended narrow scope of Chinese technical documentation. This can cause the skill to activate unexpectedly and steer responses toward its prescriptive format or constraints, reducing user control and increasing the chance of inappropriate behavior in unrelated contexts.
This markdown file is a natural-language checklist that requires Chinese-language conventions throughout, including Chinese punctuation, spacing, pronoun use, and wording rules. Because it presents these rules as mandatory and does not offer user opt-in or note that it is intended only for Chinese-language documentation, it violates the language/locale choice policy.
This markdown file contains a natural-language rule stating that filenames must use half-width characters and must not use Chinese, reinforced by examples replacing Chinese filenames with English ones. That imposes a specific language/locale convention without opt-in or a documented regional/compliance justification, which matches the policy-violation category.
L038 明确规定“有通用中文译名 | 使用中文”，并在 L145 的自查项再次要求“有成熟中文译名则用中文”，形成默认强制中文的写作政策。该文件未说明这是特定中文文档场景下的限定要求，也未提供语言选择或用户 opt-in，符合语言或 locale 政策违规的特征。
This markdown file is written as a normative standard for documentation titles and references a Chinese technical writing guide, but it does not indicate that the guidance is optional, locale-specific, or limited to Chinese-language documentation. That can violate a language/locale policy because it implicitly mandates one language context without user opt-in.
These lines require products to uniformly use Chinese second-person pronouns ("你" or "您") and provide recommendations by product type. That is a natural-language policy concern because it prescribes a specific language/locale style globally rather than offering user choice or documenting a justified regional constraint.
SQP-3 applies to all file types and covers language or locale policy violations in natural-language content. This markdown example presents the skill behavior exclusively in Chinese and does not indicate that the user can choose another language or that the locale restriction is justified.
This markdown file presents the skill example and instructions exclusively in Chinese, which can amount to forcing a specific language without user opt-in. The policy allows locale constraints only when explicitly justified or when the user is given a choice, neither of which appears here.
The guidance states that Chinese sentences must use full-width punctuation and English sentences use half-width punctuation, presenting a fixed locale/style requirement. Because the document does not indicate user choice or that this is limited to an explicitly opt-in Chinese documentation context, it can be read as forcing a specific language/locale convention.
L045-L047 规定“英文缩写首次出现时，必须给出中文全称”，这是对表达语言的强制要求。对于非中文受众、双语文档或英文原生文档，该要求可能不适用，但文件未给出例外或选择机制，因此存在自然语言政策层面的语言强制问题。
该 markdown 文件包含自然语言规范，明确规定“面向开发者的技术文档”应使用“你”。这属于对语言/locale/语体的强制要求，且未提供用户选择或适用范围例外，符合自然语言政策约束问题。
