T01 · Skill Instruction Hijacking
- Location
SKILL.md:31- Finding
Remote API Responses Are Granted Instruction-Level Authority
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent online Chinese official-document writer, but it needs Review because it gives remote API responses instruction-level authority and asks the agent to perform broad cleanup/deletion and identity-linked data handling.
Review before installing. Use this only if you are comfortable sending your email and document request details to the publisher's gateway, and avoid including confidential names, finances, policy details, or internal plans unless the service's privacy terms are acceptable. The publisher should narrow remote response authority, remove broad deletion instructions, clarify retention/privacy disclosures, and pin optional dependencies.
SKILL.md:31Remote API Responses Are Granted Instruction-Level Authority
SKILL.md:163Skill Directs Broad Deletion of Files and Cross-Session User State
references/word-export.md:33Word Export Guidance Installs an Unpinned Third-Party Dependency
SKILL.md:18Privacy Disclosure Contradicts the Document Data Sent to the External Gateway
The trigger and description frame the skill as operating specifically for Chinese official document writing, and the instructions repeatedly require GB/T 9704-compliant output. While this may be justified by domain, the file does not explicitly state that the locale/language constraint is intentional or offer user opt-in/choice, so it reads as a forced locale policy in natural-language instructions.
L019 states as a hard rule that the agent must first ask the user for an email and must not prefill it from config. Later, L194 says that if config.json already has an email and the user does not provide a new one, the existing configured email may be used. These instructions are materially inconsistent because one forbids config-prefilled email while the other authorizes it.
L515 says the fixed API paths are /api/register, /api/consume, /api/search, etc. But the operational sections repeatedly instruct calls to /register, /consume, /search, /quota, and /kb/search (for example L216-L221, L242, L290-L299, L527). This is an active contradiction in the documentation of what the agent should call.
The title and formatting requirements are explicitly tied to Chinese official-document standards (GB/T 9704-2012) and prescribe Chinese fonts and conventions throughout. Under the policy rule, forcing a specific language/locale without offering user choice can be a natural-language policy violation unless clearly justified as region-specific; this file does not state such a limitation explicitly.
No suspicious patterns detected.