simplifying-code
v2.56.0Simplifies, polishes, and declutters code without changing behavior. Use when asked to simplify, clean up, refactor, declutter, remove dead code or AI slop,...
⭐ 0· 131·0 current·0 all-time
byIlia Alshanetsky@iliaal
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (simplifying, polishing, decluttering code) matches the SKILL.md. The skill asks for repository-aware checks (git blame, imports, tests, types) which are expected for safe code simplification. No unrelated binaries, env vars, or config paths are requested.
Instruction Scope
Instructions are focused and emphasize preserving behavior, running tests, and verifying changes. They assume the agent has read/write access to the codebase, ability to run tests/type checks, and access to git metadata (git blame). This is appropriate for the task but means the agent will need repository and test-runner privileges to fully follow the process — review those privileges before granting them.
Install Mechanism
No install spec and no code files (instruction-only). Nothing will be written to disk or downloaded by the skill itself.
Credentials
The skill requires no environment variables, credentials, or config paths. The guidance to inspect code, tests, and git history is proportional to the stated purpose.
Persistence & Privilege
always is false and the skill does not request permanent presence or elevated system-wide privileges. It describes orchestration with other code-related skills but does not attempt to modify other skills' configurations.
Assessment
This skill is a coherent, instruction-only guide for simplifying code. It does not install software or request credentials, but it assumes the agent can read and modify the repository and run tests/type checks. Before installing or enabling it for autonomous runs, consider: (1) what repository and CI/test access the agent will have; (2) require human review/approval of patches or diffs before merging; (3) ensure backups/branching so accidental deletions can be recovered; and (4) limit autonomous write/merge permission unless you trust the agent and have safeguards in place.Like a lobster shell, security has layers — review code before you run it.
latestvk977gymr1jx6p09rwj8y3ve3q184tdr6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.