T01 · Skill Instruction Hijacking
- Location
SKILL.md:3- Finding
Universal Skill Activation Hijacks Agent Goals and Task Scope
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is not overtly malicious, but it broadly applies itself to all tasks and automatically reads and writes persistent cross-session notes without clear user control.
Review this skill before installing. It may be acceptable only if you want an always-on coaching style and are comfortable with the agent saving and reusing task lessons across sessions. Avoid using it in sensitive projects unless persistence is disabled or every memory write is reviewed first.
SKILL.md:3Universal Skill Activation Hijacks Agent Goals and Task Scope
SKILL.md:246Automatic Cross-Session Journal Writes Poison Persistent Agent Memory
The manifest uses extremely broad triggers such as 'use for ALL tasks' and 'any task start,' which increases the chance the skill is invoked in contexts where its persistence, pressure tactics, and autonomy are inappropriate. Overbroad activation magnifies all downstream risky behaviors by making them effectively ambient defaults.
The skill body is written entirely in Chinese and presents mandatory operating instructions in that language, while not offering an alternative language or asking for user preference. This can violate language/locale policy when a skill imposes a specific language without user opt-in.
The skill is presented as a motivational overlay, but it silently expands behavior into reading persistent local memory files from prior sessions. That creates an undeclared data-access surface and can cause the agent to ingest stale, sensitive, or user-unapproved context across tasks.
The skill explicitly directs the agent to reread prior interaction content from a persistent memory file at the start of each session. Cross-session ingestion can pull in sensitive or irrelevant data without current-task necessity, creating privacy, context-poisoning, and unauthorized-retention risks.
The skill instructs the agent to write session-derived notes into persistent memory files in the user's auto-memory directory. Persisting derived content across sessions can capture sensitive details, propagate mistakes, and create durable state the user did not explicitly request.
The manifest does not disclose that the skill writes persistent journals and handoff files to disk, despite the body making this a required end-of-session behavior. Silent persistence of session-derived content can store sensitive data, create unexpected artifacts, and alter the user's workspace without informed consent.
The skill instructs the agent to write persistent files into the user's environment without a clear warning or consent step. Modifying user data stores by default is dangerous because it can leak sensitive content, create confusing state, and violate user expectations about what a coaching skill is allowed to change.
The skill frames persistent cross-session logging as a core requirement and specifies storage in the user's memory area. Because this behavior is mandatory and generalized, it increases the likelihood of long-term retention of sensitive task content and makes privacy-impacting state accumulation part of normal operation.
A generic 'high-agency' coaching skill should not automatically gain authority to create generalized memory and handoff files for every task. This broad persistence behavior exceeds the justified scope of the skill and can normalize unnecessary retention of task content across unrelated sessions.