Synaptic Pruning

Identifies vestigial code — not just unused imports, but dead feature branches still compiled, zombie configurations nobody reads, orphaned tests that valida...

This skill's goal (find and remove 'vestigial' code) is reasonable, but the runtime instructions are broad and imply access to CI/deployment logs and production telemetry that are not described in the skill metadata. Before installing or running it: (1) insist on human review and require the skill to run in a sandbox or on a local copy of the repo first; (2) do not provide production/analytics credentials until you verify exactly which endpoints will be accessed and why; (3) require the skill author to specify the exact data sources (logs, analytics, CI) and the minimal credentials needed; (4) apply conservative thresholds (explicit N) and require an approval step before any code deletion or automated pruning; (5) keep backups and ensure changes go through code review/PRs rather than automatic removal. If the author can provide the full SKILL.md runtime steps that show constrained, read-only access patterns and explicit handling of production telemetry, that would raise confidence; if they expect the agent to autonomously query production systems without explicit credential scoping or human-in-the-loop safeguards, treat it as high risk.

Type: OpenClaw Skill Name: synaptic-pruning Version: 1.0.0 The OpenClaw skill 'synaptic-pruning' is designed for identifying and reporting dead or vestigial code within a codebase. The `SKILL.md` file contains detailed instructions for an AI agent on how to perform this analysis, including detection strategies for various types of dead code and a multi-phase pruning process. All instructions are directly aligned with the stated purpose of code analysis and health reporting. There is no evidence of malicious intent, such as data exfiltration, unauthorized command execution, persistence mechanisms, or prompt injection aiming to subvert the agent for harmful activities. The skill explicitly states 'Zero external dependencies. Zero API calls.', reinforcing its benign nature.