Security audit
Security checks for vulnerabilities and agentic risk
This is a Chinese workplace-report-writing skill made of static Markdown guidance and templates, with no evidence of hidden execution, data access, persistence, or exfiltration.
Install this if you want Chinese-language help drafting workplace reporting documents. Be aware that broad phrases like writing a document may route into this reporting workflow, and non-Chinese users may need to ask explicitly for another language.
The skill advertises very broad trigger phrases such as '写汇报'、'写文档'、'帮我写材料', which can match many ordinary writing requests before a more appropriate skill is selected. This can cause over-broad interception and unintended routing, leading the agent to apply the wrong instructions, ask irrelevant questions, or expose unrelated reference content.
The skill metadata and behavior are written as Chinese-only without indicating language negotiation or preserving the user's chosen language. If auto-selected for a non-Chinese request, it may force responses, clarifications, and routing prompts into Chinese, degrading usability and potentially causing misunderstanding of business content.
该指南全文以中文撰写并直接规定受众适配方式，没有说明是否支持用户选择其他语言或区域设置。按规则，强制特定语言且无用户 opt-in 可能构成语言/locale 政策违规。
This file presents itself as a general style guide for "all reporting scenarios" while using only Chinese, which can amount to a language/locale policy violation under the rule for natural-language constraints. There is no indication that the skill is region-specific or that users may opt into another language.
This reference file presents all user-facing instructional content in Chinese, and there is no natural-language indication that the user may choose another language or that the skill is intentionally limited to a Chinese-language context. Under the policy, forcing a specific language without user opt-in is a natural-language locale violation.
The trigger list includes broad phrases such as '横向协作' and '跨团队对齐' that can arise in ordinary workplace conversations without the user actually asking for a KO document. This can cause unintended activation, leading the agent to route the user into a specialized writing workflow and potentially ignore the user's real intent or expose internal guidance unexpectedly.
The skill metadata and content are entirely Chinese-oriented and do not indicate any language negotiation or fallback, which can force Chinese output even when the user interacts in another language. This is primarily an accessibility and reliability issue rather than a direct security flaw, but it can still cause miscommunication, incorrect outputs, or user confusion in multilingual environments.
The description says the skill triggers on phrases including “写OKR” and “双周进展”. These are broad natural phrases that may appear in ordinary workplace conversation without clearly indicating the user wants this specific skill, increasing the risk of accidental activation.
The table and entry question describe several scenarios and example trigger words, but they do not define clear non-trigger cases beyond one annual-review exception. Similar phrases like “季度复盘” or “OKR总结” may overlap with adjacent workflows, making it unclear when this skill should activate versus other reporting skills.
The trigger list includes broad phrases such as '写项目规划' and '生成技术汇报', which are common in ordinary workplace writing requests and can cause the skill to activate when the user did not intend a planning-report workflow. In an agent routing context, overbroad triggers can misroute prompts, override a more appropriate specialized skill, and lead to irrelevant or misleading output.
L003 的自然语言描述与整份技能说明均固定为中文输出语境，未见提供语言/locale 选择或根据用户偏好切换的说明。按照该规则，强制单一语言而无用户 opt-in 可能构成语言/地区策略违规。
This markdown template is entirely framed as a Chinese reporting template, including the title and all section prompts, with no indication that users may choose another language. Under the policy for natural-language violations, a skill that forces a specific language without user opt-in should be flagged unless the locale constraint is explicitly documented and justified.
The entire reference file is written in Chinese and presents skill guidance exclusively in that language, with no indication that users may choose another language or that the skill is intentionally limited to a Chinese-speaking or region-specific context. Under the policy, a language constraint without opt-in or justification is a natural-language policy violation.
The trigger list includes broad phrases such as '写改革计划', '障碍分析', and '写事后总结', which can plausibly appear in unrelated writing or planning contexts. That increases the chance this skill activates when the user did not intend a postmortem flow, causing incorrect routing, context capture, and potentially misleading outputs in a sensitive incident-reporting domain.
The skill description is written to operate in Chinese without indicating language fallback or user choice, which can cause the agent to respond in an unexpected language. In practice this is more of an accessibility and usability control issue than a security flaw, but it can still lead to misunderstanding in incident documentation where precision matters.
This markdown template is entirely written in Chinese and provides no indication that another language can be used. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation unless the locale restriction is explicitly justified.
The manifest description is entirely in Chinese and defines Chinese trigger phrases for activation, but it does not indicate that the skill is Chinese-only by user choice or provide an option for other languages. This creates a natural-language locale policy issue because the skill appears to require a specific language without explicit opt-in or justification.
This markdown template is entirely written in Chinese and presents the review structure as mandatory content, with no indication that users may choose another language. Under the policy rules, forcing a specific language without user opt-in is a natural-language policy violation unless the locale restriction is explicitly justified.
SQP-3 applies to all file types and covers language or locale policy violations. This markdown file presents all instructions solely in Chinese and does not indicate that the skill is region-specific or that users may choose another language, which can amount to forcing a specific language without opt-in.
This markdown template forces a specific language/locale for all users through its headings and instructions, but does not provide any opt-in, alternative language option, or justification that it is intended only for a Chinese-speaking context. Under the stated policy, language-specific content without user choice or documented regional scope is a natural-language policy concern.
This markdown file is entirely written in Chinese and presents the guidance as the default interaction language, with no indication that users may choose another language or locale. Under the policy rule for natural-language violations, a skill that effectively forces a specific language without user opt-in should be flagged unless the locale restriction is justified or optional.
No suspicious patterns detected.
