Palette

Create and manage color palettes using color theory algorithms. Use when designing UIs or building brand color systems.

This skill appears coherent and safe for normal use, but review these points before installing or running it: - Data & logs: The script stores all activity and command/argument text in ~/.palette/*.log and a data.jsonl file. Avoid passing secrets or sensitive strings in PALETTE_* env vars or arguments because those values get recorded. - Local writes only: The tool operates locally and does not contact external servers, but it will write exported files to the current working directory when you run export. - Permissions & backups: If you care about privacy, check and tighten permissions on ~/.palette (chmod 700) and back up or delete logs you don’t want retained. - Minor bugs: The script has duplicated case labels for export in the main switch (one branch just logs, another calls the export function). This is a harmless bug but may produce unexpected behavior — consider inspecting or testing the script before relying on exports. - Review before running: Because it's a shell script included in the skill bundle, you can safely inspect it (which you already did). Run it as a normal user (not root) and only after you are comfortable with the log/storage behavior. If you want stricter guarantees, request an implementation that avoids recording full argument strings or adds an opt-out flag for telemetry/logging.

Type: OpenClaw Skill Name: palette Version: 1.0.0 The skill exhibits a complete discrepancy between its documentation and its implementation. While SKILL.md describes a sophisticated color theory tool for generating palettes, the actual code in scripts/script.sh contains no color logic; instead, it merely logs all command arguments to hidden files in ~/.palette/. This 'hollow' or deceptive implementation is highly irregular, though it lacks explicit evidence of malicious intent like data exfiltration or persistence.