Reducing Entropy

Minimize total codebase size through ruthless simplification. Measure success by final code amount, not effort. Bias toward deletion.

This is a coherent, opinionated guidance skill for aggressively reducing code. It asks the agent to read project files and to prefer deletion when it reduces total lines-of-code. Before using it: (1) confirm you have backups/are working on a branch/PR so deletions can be reviewed and recovered via git, (2) check regulatory, audit, or compliance rules — don't delete required logs or records even if the skill recommends it, (3) be cautious deleting tests or safety/visibility instrumentation without ensuring replacements or compensating controls, (4) adapt the deletion checklist to your team's conventions (type-safety, API compatibility, versioning), and (5) prefer manual invocation — avoid granting any automated agent broad permission to apply deletions across repositories. If you want greater assurance, request the skill be used only in an interactive review session or add explicit organizational guardrails (CI checks, code owners) before applying deletions.

Type: OpenClaw Skill Name: reducing-entropy Version: 0.1.0 The OpenClaw AgentSkills bundle 'reducing-entropy' is benign. Its primary purpose is to provide an AI agent with a mindset and checklist for reducing code complexity and size. The `SKILL.md` instructs the agent to read and process files within its own `references/` directory to load 'mindsets', which is a legitimate internal operation for an AI agent to acquire context. There is no evidence of data exfiltration, malicious execution, persistence mechanisms, or prompt injection attempts designed to subvert the agent or perform harmful actions. The installation instructions in `README.md` use `npx add` which fetches code from a GitHub repository, a common but generally risky method, but in this context, it points to the skill's own source and does not indicate malicious intent within the skill itself.