Security audit
Security checks for vulnerabilities and agentic risk
This is a narrow BWC Chinese-English translation skill with no executable code or sensitive system access, though its generic translation triggers could cause accidental use.
Install this if you want BWC product or API documentation translated with locked terminology. Be aware that generic translation triggers may activate it too broadly, so confirm the request is actually about BWC when using it.
The instructions require that every occurrence of "BWC"/"bwc" be rendered as fixed target-language terms and explicitly say to "Never leave the bare acronym in translated prose." This enforces a specific language/locale choice in output rather than allowing user preference or preserving the source acronym when desired.
The description states that the skill is dedicated to Chinese-English bidirectional translation and prescribes how BWC terms should be rendered in the target language. This imposes a language/locale behavior without any indication that users can choose or opt in to language preferences.
The trigger phrase "翻译" is extremely broad and can match many ordinary user requests unrelated to this specialized BWC translation skill. That can cause unintended invocation, leading the assistant to apply domain-specific terminology or workflow when the user did not request this skill, which is a prompt-routing and reliability issue.
The trigger phrase "translate" is too generic and is likely to overlap with common everyday requests. In a skill that imposes specialized terminology and style rules, accidental activation can misroute general translation tasks and produce incorrect or overly constrained outputs.
The text explicitly requires every concept to map to one approved Chinese term and one approved English term, and forbids re-translation. This imposes a fixed bilingual language policy without user opt-in or a documented justification that the glossary is restricted to a specific regional or compliance context.
The document states that the rules apply specifically to BWC technical and API documentation in Chinese and English, making this a mandatory language constraint. Under the policy, forcing a specific language or locale without user choice can be a natural-language policy concern unless clearly justified as region- or domain-specific.
