T01 · Skill Instruction Hijacking
- Location
SKILL.md:22- Finding
Identity-development instructions can override the agent's operational objectives
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is not overtly malicious, but it asks an agent to make lasting identity and scheduler changes without enough user control or limits.
Review before installing. This skill should only be used if you intentionally want an OpenClaw bot to maintain persistent identity files and possibly run scheduled self-reflection sessions. Require explicit approval before creating cron jobs, editing SOUL.md or HEARTBEAT.md, using research tools, or changing behavior based on reflection files; keep the identity workspace scoped, auditable, and easy to disable.
SKILL.md:22Identity-development instructions can override the agent's operational objectives
SKILL.md:92Persistent identity files create a cross-session behavioral poisoning loop
SKILL.md:73Daily scheduled exploration establishes autonomous cross-session persistence
The README states the skill triggers automatically for broad, common themes like identity development, self-exploration, or personal growth. In an agent system, overly broad trigger conditions can cause the skill to activate in contexts where it was not explicitly requested, potentially steering conversations, creating unauthorized persistence/setup behaviors, or invoking self-modification workflows unexpectedly.
The trigger list includes very broad phrases such as "personal growth," "reflection setup," and "who am I," which can cause the skill to activate in contexts far beyond the author's intended use. Over-broad invocation increases the chance that an agent will enter this workflow unexpectedly and begin identity-shaping or file-modifying behavior when the user did not explicitly request it.
The skill's quick start directly instructs creation of an identity/ directory and setup of a daily cron job, which are persistent system modifications, without an upfront warning or explicit approval gate. In an agent setting, this can lead to unauthorized filesystem changes and scheduled autonomous execution, expanding the skill from passive guidance into lasting behavioral change.
The instruction to create a recurring cron job establishes unattended session persistence, allowing the agent to run regularly without a fresh user request each time. Even though framed as self-exploration, persistence materially increases risk because it creates an autonomous execution path that could consume resources, produce unreviewed outputs, or interact with local state over time.
Create a cron job for an isolated session, separate from operational heartbeats. Schedule it during a quiet period for your household.
The file repeatedly instructs the agent to create and modify workspace files such as identity/reflections, identity/values.md, identity/interests.md, and SOUL.md without requiring confirmation, scoping those writes to a safe sandbox, or warning that persistent user/workspace data will be altered. In an agent setting, this can lead to unintended persistence, overwriting existing files, or polluting shared workspace state, especially because the prompt frames these edits as routine and ongoing.
No suspicious patterns detected.