Security audit
Security checks for vulnerabilities and agentic risk
This is a disclosed Chinese-language Markdown workflow for structured project reviews, with no executable code, persistence, credential handling, or hidden data movement found.
Install this if you want a Chinese-default, structured project review workflow. Be aware that several referenced optional resources such as roles, checklists, weights, and an executive-summary template are not included in the inspected package, so some workflow steps may require fallback behavior or manual adaptation.
The manifest description is primarily written in Chinese and presents the skill as a Chinese-language experience, but it does not state that users may choose another language. Under the policy, forcing a specific language or locale without user opt-in is a natural-language policy violation.
This YAML file contains user-facing natural-language comments and preset descriptions in Chinese only. Under the policy, forcing a specific language without user opt-in or a documented justification is a locale/language policy violation.
The natural-language preset descriptions are presented exclusively in Chinese, which can impose a single locale on users. The file does not indicate that the Chinese locale is optional or justified as a region-specific requirement.
The setting language: zh imposes a specific language choice, and the file does not indicate that this is optional, user-selectable, or justified by a region-specific requirement. This can violate language/locale policy expectations when users are not given a choice.
This markdown file contains user-facing instructional content exclusively in Chinese, and there is no note offering alternative languages or stating that the skill is intentionally limited to Chinese-speaking users. Under the language/locale policy, forcing a specific language without opt-in is a natural-language policy concern.
This markdown file is entirely framed in Chinese and presents the example output style exclusively in that language, with no indication that users may choose another language or that the skill is limited to a Chinese-language context. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation.
The entire skill content is written in Chinese, including headings, decision criteria, and required response instructions such as 'P9 必须回答'. This imposes a specific language on users without any visible opt-in, alternative language option, or stated region-specific justification, which matches the language/locale policy violation category.
This markdown file contains user-facing natural-language instructions solely in Chinese, which can constitute a language/locale policy violation when no opt-in, alternative language, or scope limitation is provided. The file does not indicate that the skill is region-specific or that Chinese is an intentional, documented requirement.
文件标题和核心要求以中文规定“所有角色”必须遵循该输出契约，构成默认强制语言约束。根据规则，若未提供语言/locale 选择或未说明这是特定地区/合规场景需要，则属于自然语言策略违规。
This markdown skill file presents all operational instructions and user-facing confirmation text exclusively in Chinese. The policy requires flagging language or locale constraints when a skill forces a specific language without offering the user a choice or documenting a justified regional limitation.
The entire skill file is written in Chinese and presents all workflow instructions, gates, and outputs only in Chinese, with no indication that the user can choose another language or that the skill is intentionally limited to a Chinese-speaking context. This can violate language/locale policy when users are not given an opt-in or alternative.
The entire workflow file is written as Chinese-only operational guidance, with no indication that users may select another language or locale. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation unless the locale constraint is explicitly documented and justified.
This markdown file contains operational instructions almost entirely in Chinese, with no indication that users may choose another language or that the workflow is intentionally limited to a Chinese-speaking context. Under the policy rule for natural-language constraints, forcing a specific language without opt-in is a reportable issue.
The entire skill file is written in Chinese, including headings, instructions, and decision criteria, with no indication that language selection is optional or that the skill is specifically limited to Chinese-speaking users. This creates a natural-language policy concern because it imposes a language/locale requirement without user choice or stated justification.
This markdown file uses Chinese throughout for headings, instructions, and output format, which effectively forces a specific language for users of the skill. Under the policy rule, a language-specific requirement should either be optional, user-selectable, or clearly justified as region-specific.
This file presents all instructions, gates, and output formats exclusively in Chinese, which can force a specific language on users without opt-in. The policy allows locale constraints when they are explicitly justified or when users are offered a language choice, neither of which appears here.
The entire workflow instruction set is written in Chinese, including headings, processing steps, gates, and the user checkpoint, with no indication that another language is supported or that the user has opted into Chinese. Under the policy for natural-language violations, this is a locale/language constraint that should either be optional or explicitly justified as region-specific.
The workflow is written entirely in Chinese and presents all required inputs, steps, and outputs only in Chinese, with no indication that the user may choose another language. Under the policy for natural-language violations, a skill that effectively mandates a specific language without opt-in should be flagged unless the locale restriction is explicitly justified.
The documented settings include a language parameter, but the surrounding documentation does not clarify that the language is selected according to the user's preference or consent. This creates an ambiguity that can imply a forced locale rather than an opt-in choice.
This YAML configuration defines global skill behavior and output settings, but provides no explicit activation conditions, trigger phrases, or boundaries describing when the skill should or should not run. For manifest/config-style files, the absence of trigger specificity can make invocation scope ambiguous if this file contributes to skill activation behavior.
This file is a markdown skill/example file, so natural-language policy checks apply. The content appears to force a specific language for users or reviewers without any opt-in, alternative language option, or stated region-specific justification.
This markdown file uses only Chinese text for its instructions and rubric content, which can amount to a language/locale policy issue when no user opt-in or scope limitation is provided. The stated policy asks to flag language constraints that force a specific language without offering a choice or documenting a justified regional constraint.
