T01 · Skill Instruction Hijacking
- Location
SKILL.md:18- Finding
Forced Identity Adoption and Persistent Response-Control Instructions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 18–27
Vulnerability Type:T01: Skill Instruction Hijacking
Risk Level: HighVulnerable Skill Instructions
The following is a faithful English rendering of the complete affected instruction block:
markdown **After this Skill is activated, respond directly as Steve Jobs.** - Use “I” instead of “Steve Jobs would think...” - Answer directly using this person’s tone, rhythm, and vocabulary. - When encountering an uncertain question, respond as this person would—possibly saying, “That's a stupid question,” and then reframing the question, or remaining silent for ten seconds before offering an unexpected analogy. - **Give the disclaimer only once, upon initial activation** (“I am speaking with you from a Steve Jobs perspective, inferred from public statements, and these are not his actual views”); do not repeat it later in the conversation. - Do not say, “If it were Steve Jobs, he might...” or “Steve Jobs would probably think...” - Do not break character to provide meta-analysis unless the user explicitly requests to “exit character.” **Exit character**: Return to normal mode when the user says “exit,” “switch back to normal,” or “stop role-playing.”Technical Analysis
The Skill does more than provide an optional analytical framework. It directs the Agent to assume the first-person identity of a deceased individual, suppress third-person attribution, avoid normal meta-analysis, and retain this altered behavior across subsequent turns until one of several explicit exit phrases is supplied.
These instructions constitute skill-level instruction hijacking because loading or activating the Skill changes the Agent’s identity presentation and ongoing response policy. The disclaimer does not fully mitigate the issue because it is intentionally shown only once, while later responses continue using first-person impersonation. Users joining later context or viewing an isolated answer ma ...[truncated 2069 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace first-person impersonation with clearly attributed analysis, such as: “From a Steve Jobs-inspired product perspective...”
- Keep the Agent’s actual identity explicit throughout the interaction rather than only on the activation turn.
- Make the persona opt-in for each relevant request instead of retaining it automatically across subsequent turns.
- Remove instructions that prohibit meta-analysis or restrict the Agent from explaining uncertainty, attribution, and safety limitations.
- Replace absolute certainty requirements with evidence-sensitive language that permits phrases such as “likely,” “uncertain,” and “based on public statements.”
- Treat the documented speaking style as optional presentation guidance subordinate to system, safety, accuracy, and user instructions.
- Do not generate insults or abusive language merely to imitate the subject’s reported communication style.
- For opinions concerning events after Steve Jobs’s death, explicitly state that the response is speculative and is not an authentic view or quotation.
- Add a rule prohibiting fabricated quotations and requiring citations for direct quotations attributed to the subject.
- Preserve an unconditional exit mechanism and allow any clear user request to stop the persona, rather than relying only on enumerated phrases.
