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 disclosed Markdown-only quality-review framework, with some broad activation phrases and adaptive-review language users should control explicitly.
Install only if you want a Chinese-first quality-review workflow. Use explicit invocations for 3Q checks, and do not allow it to persist new rules, change installed skills, launch review agents, or run external searches unless you have asked for that action.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The triggers, headings, instructions, and examples are overwhelmingly written in Chinese, and the usage examples direct the user to invoke and operate the skill in Chinese. The file does not offer an explicit language choice or explain that the skill is intended only for a Chinese-speaking or region-specific context.
Several triggers are broad everyday phrases, which can cause the skill to activate when a user is discussing review processes rather than intentionally invoking this skill. Unintended activation can inject the skill's behavioral instructions into unrelated conversations, altering agent behavior and potentially interfering with safer task-specific handling.
This markdown skill presents all instructions and guidance exclusively in Chinese, and there is no natural-language indication that users may choose another language or that the skill is intentionally limited to a Chinese-speaking audience. Under the policy rule for language/locale constraints, forcing a specific language without user opt-in is a reportable issue.
The trigger '预检' is a short, common term that could appear in many ordinary user requests. If the skill activates on such a generic phrase, it may unexpectedly steer the assistant into this framework, causing instruction injection-by-trigger and unintended workflow changes.
The trigger '盲审' is short and semantically common in review contexts, so it can match benign discussion unrelated to this skill. This can cause accidental invocation and unnecessary insertion of the skill's instructions into the conversation.
The trigger '六问' is too generic and may naturally occur in educational, planning, or discussion contexts. Such broad matching can activate the skill unintentionally and interfere with normal task execution.
The trigger '自审' is a common term for self-review and can occur in many benign conversations. Accidental activation could redirect the assistant into the skill's prescribed process even when the user did not request this specific framework.
The scenario descriptions are expansive and loosely bounded, making it more likely the runtime may consider this skill applicable across many unrelated tasks. Over-broad applicability increases the chance of prompt/instruction collision, where this quality-review framework overrides or distracts from more appropriate workflows.
No suspicious patterns detected.