WP Multitool — WordPress Optimization Toolkit
Analysis
This is a coherent WordPress WP-CLI helper; its cleanup and configuration commands are powerful but disclosed and require user confirmation.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
Always confirm with the user before executing: - `wp transient delete` ... - `wp post delete --force` ... - `wp db optimize` ... - `wp config set`
These WP-CLI commands can delete database rows, permanently remove revisions/posts, lock/optimize tables, or change wp-config.php. The artifact explicitly marks them as requiring confirmation, so this is a user-awareness note rather than a concern.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
"permissions":{"read":true,"write":true,"write_operations":["delete_transients","delete_revisions","delete_orphaned_meta","optimize_tables","modify_wp_config","modify_plugin_options"],"requires_user_confirmation":true}The skill declares WordPress read/write authority and specific mutation operations. This authority is aligned with the toolkit's purpose and is disclosed with a confirmation requirement.
