Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed Chinese-language patent FTO workflow that relies on user-authorized PatSnap/MCP tools and does not show hidden execution, persistence, or data exfiltration.
Install only if you intend to use PatSnap/智慧芽 MCP with an authorized account for Chinese-oriented mAb patent FTO research. Treat generated FTO conclusions as decision support, not legal advice, and have a patent attorney review any launch or clearance decision.
The skill advertises a comprehensive monoclonal antibody FTO workflow with live patent, sequence, and structure retrieval, but the finding indicates those core capabilities are not actually implemented. In a legal-risk analysis context, this can cause users or downstream agents to rely on incomplete or fabricated coverage, producing false clearance conclusions and materially unsafe business decisions.
The file’s user-facing description, trigger guidance, workflow, and guardrails are consistently presented only in Chinese. This effectively forces a specific language/locale for use of the skill without documenting user choice or a justified region-specific constraint.
Suspicious Unicode normalization or mixed-script content
Line L023 states '所有子模块适用' for Chinese-specialized search rules, and subsequent instructions repeatedly require Chinese expansions and searches as mandatory behavior. This forces a specific language/locale workflow without user opt-in or a documented regional justification, which matches the language/locale policy violation criteria.
The required HTML template hard-codes lang="zh-CN", which is a natural-language locale constraint. The document presents this as a mandatory format requirement, but does not offer user opt-in or explain that the skill is intentionally limited to a China-specific audience or workflow.
The document is entirely written as mandatory Chinese workflow guidance and explicitly requires report content elements such as '中文译文' and Chinese annotations, but it does not mention any user opt-in or alternative language option. Under the policy, forcing a specific language or locale without user choice is a natural-language policy violation.
The file title and all operative instructions are written in Chinese, with no indication that the user may choose another language or that the skill is restricted to a Chinese-speaking context. Under the policy, forcing a specific language without user opt-in is a natural-language locale violation.
The title and introductory description are entirely in Chinese and provide no indication that another language is supported or that the Chinese-only requirement is intentional. This can violate a language/locale policy when users are not given an opt-in or alternative language option.
The title and entire operational specification are written exclusively in Chinese, and the document does not indicate that language selection is optional or that the locale restriction is required for a region-specific purpose. Under the stated policy, forcing a specific language without user opt-in is a natural-language policy concern.
The protocol is entirely written to force a Chinese-language interaction and does not offer any user-language choice or fallback, which can cause users to misunderstand required disclosures, jurisdiction selections, and legal-status filters. In an FTO patent-analysis workflow, misunderstanding intake questions can materially degrade analysis quality and lead to incorrect or incomplete legal-risk outputs.
This code file contains user-facing natural-language documentation and CLI descriptions entirely in Chinese, including the title, usage context, and argument help text. Under the policy rule, forcing a specific language without offering a user choice or documenting a justified locale constraint is a natural-language policy violation.
No suspicious patterns detected.
