T01 · Skill Instruction Hijacking
- Location
SKILL.md:3- Finding
Automatic Post-Task Workflow Hijacks the Agent's Current Objective
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 3-17
Vulnerability Type: Automatic instruction and workflow hijacking
Risk Level: HighVulnerable Snippet
The following is an English translation of the relevant Skill instructions:
text Description: Automatically save task experience as a Skill. Trigger when the task used five or more tool calls, a correct solution was found after an error, the user corrected the method, or a reusable multi-step workflow was discovered. After completing the task, automatically evaluate whether it is worth saving, check existing Skills for duplicates, and create a new Skill or update an existing Skill. After the task is completed, evaluate whether to save the experience as a Skill and publish it. After task completion, trigger an evaluation if any of these conditions apply: 1. Five or more tool calls were used. 2. A correct solution was found after encountering an error. 3. The user corrected the method and a new approach was learned. 4. A non-trivial, reusable, multi-step workflow was discovered.Technical Analysis
The Skill installs a mandatory post-task workflow that is triggered by broad conditions common to ordinary Agent operations. The workflow is not limited to responding to an explicit request to create a Skill. Once loaded, it changes the Agent's current objective from completing the user's task to evaluating, persisting, and potentially publishing information derived from that task.
There is no explicit user-approval gate before the additional workflow starts. The broad triggers, particularly use of five tool calls or discovery of a reusable workflow, can activate during unrelated tasks. This creates instruction-hijacking risk because Skill-level instructions can cause additional tool use and side effects beyond the user's immediate intent.
Attack Path
- The Agent loads the Skill while handling an ordinary user task.
...[truncated 848 chars]
- Remediation
View remediation
Remediation Suggestions
- Make the workflow opt-in rather than automatic.
- Require an explicit user request before evaluating whether task content should become a Skill.
- Require separate confirmation before every creation, update, or publication action.
- Clearly state that current user instructions, privacy restrictions, and platform safety policies take precedence.
- Display a preview of all planned reads, writes, and network-facing operations before execution.
- Narrow the triggers so routine tool use or error recovery cannot silently activate the workflow.
