Tp2
- Category
- MCP Tool Poisoning
- Confidence
- 85% confidence
- Finding
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
- Content
Security audit
Security checks for vulnerabilities and agentic risk
This is a markdown-only Chinese skill for improving other skill prompts, with no hidden execution, credential access, network use, or persistence.
Install this if you want a Chinese-language assistant for improving existing Skill.md files. Review and possibly narrow the trigger phrases before using it in a large shared skill set, and expect it to produce proposed skill text rather than automatically modify other skills.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
This markdown file contains user-facing deployment instructions exclusively in Chinese, and nowhere indicates that users may choose another language or that the locale restriction is intentional. Under the policy rule, forcing a specific language without user opt-in is a natural-language policy concern.
The trigger set contains broad phrases such as requests about fixing a skill or repairing entry behavior, which can overlap with many ordinary support or editing requests. In a multi-skill environment, overly general triggers can cause unintended routing, skill hijacking, or collisions with adjacent skills, leading to incorrect execution paths and unstable behavior.
The trigger phrase at this location is vague enough to resemble common everyday speech, increasing the chance that normal user requests accidentally invoke this skill. In a shared agent ecosystem, such ambiguity can crowd out more appropriate skills and create denial-of-service-like routing instability for legitimate specialized workflows.
The entire test prompt file is written as if the skill and its evaluations should operate in Chinese only, with no indication that users may choose another language or locale. Under the policy rule, forcing a specific language without offering a choice is a natural-language policy violation.
This markdown validation report presents all user-facing natural language in a single forced language/locale. Under the policy, language constraints should either offer user opt-in/choice or be clearly documented as justified for a region-specific use case, which is not present here.
The instruction "frontmatter 中统一中文名,英文名降级为 alias" imposes a Chinese-language naming policy as a default requirement. The file does not indicate user choice, opt-in, or a documented region-specific justification for this locale constraint.