Security audit
Security checks for vulnerabilities and agentic risk
This skill coherently helps Chinese K12 teachers plan review schedules and only saves plans after explicit teacher confirmation.
Install this for Chinese-language, mainland China K12 teacher workflows. Before use in another country, language, curriculum, or legal environment, localize the crisis referral numbers, grade and curriculum assumptions, and data-consent rules. Teachers should review saved review plans because the skill intentionally reads class learning data and writes persistent review schedules only after confirmation.
The manifest description, display fields, and user-facing trigger examples are presented only in Chinese, which effectively forces a specific language/locale for activation and use. Under the policy, language constraints should either be user-selectable or explicitly documented and justified as region-specific.
The description states the workspace contract using Chinese-only terminology, and many downstream enums and field descriptions are defined exclusively in Chinese, implying the skill expects a fixed language/locale. Under the policy, forcing a specific language without user opt-in or a clearly documented locale-specific justification is a natural-language policy concern.
The entire shared instruction file is written as normative guidance in Chinese and contains prescriptive response wording such as asking and explaining to students in Chinese. There is no indication that users may choose another language or that the locale restriction is limited to a justified region-specific deployment.
The text declares this file as the single source of truth for all terminology and requires all related documentation and schemas to reference its definitions, which are entirely in Chinese. This enforces a specific language/locale at the organizational level without any opt-in, alternative locale, or stated region-specific justification.
This markdown file includes guidance for when skills are deployed to other languages or regions, but it does not define narrow trigger phrases or clear negative examples for when this localization policy should apply. Under the vague-trigger rule for markdown files, broad applicability language can cause inconsistent or unintended use across skills.
No suspicious patterns detected.
