Self-Modification
High
- Category
- Rogue Agent
- Content
If a lamp was repaired, re-paired, or moved to another network, assume the `local_key` may have changed. Read `KEY_EXTRACTION.md` and `ONBOARDING.md`, refresh the key, test with the preferred CLI first (`lampctl <lamp> status`), then use `tuya_test_lamp.py --probe` if Python fallback is needed, and finally update `tuya_lamps.json`. ## Portability note This skill intentionally prefers explicit standard project paths so it can still work after being copied into a separate OpenClaw skills directory. If a local installation uses a different layout, update this SKILL.md so the binary and project paths match that environment. ## Current live lamps - `kitchen`
- Confidence
- 90% confidence
- Finding
- The skill explicitly instructs the agent to 'update this SKILL.md' to match the local environment. Allowing a skill to direct self-modification of its own instructions creates a persistence and trust-boundary problem: environment-derived or attacker-influenced data could be written back into the skill, causing future runs to execute altered commands or trust poisoned paths. In this context, the risk is increased because the file contains executable command patterns and absolute binary paths, so tampering can directly redirect later device-control operations.
