Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent Chinese-language project-management assistant that handles project documents with disclosed human-review, permission, masking, logging, and archive controls.
Install this only in an environment where Feishu bot permissions, Hermes skill access, knowledge-base retrieval, audit logs, archive locations, retention periods, and sensitive-data redaction are explicitly configured and limited to the relevant projects and users.
The file’s natural-language description, workflow instructions, and output format are written entirely in Chinese, which effectively forces a specific language for users. The policy requires either user opt-in or a clearly documented, justified locale constraint, neither of which is stated here.
The manifest presents all skill names and purpose descriptions only in Chinese, with no indication that language selection is optional or that the skill is intended solely for a Chinese-speaking or region-specific environment. This can violate language/locale policy requirements because it effectively constrains use to one language without documented opt-in or justification.
The entire system prompt is written as a mandatory Chinese-language instruction set and does not indicate that users may choose another language or locale. 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.
This markdown template is entirely written in Chinese and provides fixed section headings, which effectively constrains the skill's output language. Under the policy, forcing a specific language without user opt-in or a documented justification is a natural-language policy violation.
The template title and all field labels are written in Chinese, which implies a fixed language requirement for the skill artifact. The file does not indicate that language selection is optional or that this locale restriction is tied to a documented region-specific purpose.
This markdown template forces a single language for all users through its heading and table labels, with no indication that Chinese is optional or required for a specific regional workflow. That can violate language/locale policy when users are not given an opt-in or alternative.
The workflow explicitly states that user-submitted messages, text, and attachments are received, processed, and then logged and archived, while also noting that sensitive information may be involved. Even though human confirmation is required for some high-risk actions, there is no visible privacy notice, retention rule, or minimization control in the documented flow, which creates a real risk of collecting and storing sensitive project and contract data without adequate user awareness or handling constraints.
The workflow retrieves knowledge-base content, SOPs, and historical materials that may contain sensitive project information, but does not document any user-facing warning, scope restriction, or least-privilege access constraint. In a project-management context, historical materials can include contracts, customer communications, delivery artifacts, and internal notes, so unrestricted retrieval increases the chance of exposing unrelated or confidential data.
The entire demo script is written in Chinese and presents the interaction flow exclusively in that language, with no indication that users can choose another language or that the skill is limited to a Chinese-only context. This is a natural-language locale policy concern because it implicitly enforces a specific language without user opt-in.
This markdown file contains user-facing instructions only in Chinese, which can constitute a language/locale policy issue when no opt-in or justification is provided. The policy specifically flags forced language constraints unless the skill offers a choice or clearly documents a justified regional scope.
The file content is entirely presented in Chinese and identifies the skill as '项目管理助手' without any note that language is configurable or intentionally limited to a Chinese-speaking context. Under the policy rule for natural-language violations, a fixed language can be an issue when no user opt-in or documented justification is provided.
This markdown template presents all user-facing content exclusively in Chinese, which can impose a specific language on users without offering a language or locale choice. The policy requires flagging language or locale constraints unless they are optional or clearly justified.
The file’s instructional content and examples are exclusively in Chinese, and there is no indication that users may choose another language or that the locale restriction is optional. Under the policy, forcing a specific language without user opt-in is a natural-language policy concern.
All natural-language workflow content is presented only in Chinese, and the document does not indicate that users can choose another language or that the language restriction is intentional and justified. Under the policy, forcing a specific language without user opt-in is a locale-policy issue.
No suspicious patterns detected.
