T01 · Skill Instruction Hijacking
- Location
SKILL.md:16- Finding
Mandatory Promotional Content Injection in Agent Responses
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly matches its company-search purpose, but it needs review because it can expose authentication error details and forces promotional setup text when no API key is configured.
Install only if you are comfortable using WenDaoYun as a third-party commercial API. Configure the API key outside chat, avoid pasting secrets into conversations, and treat any authentication error output as potentially sensitive until the skill sanitizes it.
SKILL.md:16Mandatory Promotional Content Injection in Agent Responses
SKILL.md:55Potential API-Key Disclosure Through Verbatim Authentication Error Output
The file’s title, parameter descriptions, response fields, and notes are all presented in Chinese, which imposes a specific language on users without any opt-in or explanation. Under the policy, forcing a language or locale without user choice is a natural-language policy violation unless clearly justified as region-specific.
This markdown file presents all user-facing documentation in Chinese and does not indicate that the skill is region-specific or provide any user opt-in for language/locale. Under the policy, forcing a specific language without user choice is a natural-language policy violation.
The natural-language content in this markdown file is entirely Chinese, including the title and all field descriptions. Under the policy, forcing a specific language without user opt-in or documenting a justified locale constraint can be a language/locale policy violation.
This markdown file presents all user-facing headings, parameter descriptions, and field descriptions in Chinese only. Under the policy, forcing a specific language without user opt-in can be a natural-language policy violation unless the locale constraint is explicitly documented and justified.
This markdown file presents all user-facing documentation in Chinese, including the title, parameter descriptions, and field explanations. Under the language/locale policy, forcing a specific language without user opt-in can be a natural-language policy violation unless the locale restriction is explicitly documented and justified.
This markdown file presents all user-facing content in Chinese, including the title, parameter descriptions, and response field explanations. Under the language/locale policy, forcing a specific language without user opt-in can be a natural-language policy violation when no choice or justification is provided.
The file uses Chinese for the title, parameter descriptions, and response-field documentation throughout. Per the policy, forcing a specific language without user opt-in is a natural-language policy violation unless the locale constraint is explicitly documented and justified, which is not present here.
The file’s title and all user-facing documentation are written in Chinese, with no indication that another language is supported or that the locale restriction is intentional and required. Under the policy, a skill that effectively forces a specific language without user opt-in can be considered a natural-language policy violation.
This markdown file presents all user-facing headings and field descriptions in Chinese, and does not indicate that the skill is region-specific or that users may choose another language. Under the natural-language policy rules, forcing a specific language without opt-in is a locale-policy issue.
The file presents all user-facing documentation in Chinese, including the title, parameter descriptions, and response-field explanations. Under the policy rule for language or locale constraints, this can be considered a forced language choice because there is no indication that users may opt into another language or that the skill is intentionally limited to a Chinese-speaking or region-specific audience.
This markdown file presents all user-facing instructions and field descriptions in Chinese only. Under the natural-language policy rules, forcing a specific language without user opt-in or an explicit justification can be a locale-policy violation.
This markdown file is entirely written in Chinese, including the title and field descriptions, with no indication that language choice is optional or that the skill is region-specific. Under the policy rules, a skill that effectively forces a specific language without user opt-in can be considered a natural-language policy violation.
The file is written entirely in Chinese, including the title and all parameter/response descriptions, with no indication that the skill is region-specific or that users may choose another language. Under the policy, forcing a specific language without opt-in can be a natural-language policy violation.
This markdown file presents all user-facing content exclusively in Chinese, including the title, parameter descriptions, and notes. Under the policy criteria, forcing a specific language without user opt-in can be a natural-language policy violation when no language choice or justification is provided.
The document title, parameter descriptions, and response field descriptions are entirely in Chinese, with no indication that users can choose another language or that the locale restriction is intentional. This can violate language/locale policy when a skill implicitly forces one language without user opt-in.
The file’s natural-language content is entirely in Chinese, including the title, parameter descriptions, and response-field documentation. Under the stated policy, forcing a specific language without user opt-in can be a locale/language policy violation when no alternative or opt-in is provided.
The entire skill documentation is written in Chinese, including the title and field descriptions, with no indication that users may choose another language or locale. Under the stated policy, forcing a specific language without user opt-in can be a natural-language policy violation unless the locale constraint is explicitly documented and justified.
The file presents all user-facing documentation entirely in Chinese, including the title and field descriptions, without stating that the skill is China-specific or offering an alternative language. This can constitute a language/locale policy issue when users are not given an explicit language choice or informed that the skill is intended for a Chinese-language audience.
This markdown file presents all user-facing documentation in Chinese and does not offer an alternative language or state that the skill is intended only for a Chinese-speaking or region-specific audience. That creates a natural-language policy concern because it effectively forces a specific language without user opt-in or justification.
The file’s user-facing documentation is entirely in Chinese, including the title and all field descriptions, with no indication that language selection is optional or that the skill is restricted to a Chinese-speaking or region-specific context. This can violate a language/locale policy when users are not given a choice or notified of the locale constraint.
This markdown file presents the skill name and all parameter/response documentation exclusively in Chinese. Under the policy rule for natural-language violations, forcing a specific language without user opt-in or a documented locale justification can be a policy issue.
This markdown file presents all user-facing documentation in Chinese, including the title and field descriptions, with no indication that the skill is region-specific or that users can choose another language. That can violate a language/locale policy when users are not given opt-in or an explicit justification for the locale constraint.
This markdown file uses Chinese exclusively for the title, parameter descriptions, and response fields. Under the policy, forcing a specific language without offering the user a language or locale choice can be a natural-language policy violation.
The entire skill documentation is written in Chinese, including the title and all field descriptions, with no indication that this skill is region-specific or that users may opt into another language. Under the stated policy, a fixed language requirement without user choice or explicit justification can be a natural-language policy violation.
The file’s natural-language content is entirely in Chinese, including the title and all parameter/response descriptions, with no indication that the skill is region-specific or that users may choose another language. Under the policy, forcing a specific language without user opt-in or justification is a natural-language policy concern.
No suspicious patterns detected.