What problem does it solve?
Installing WordPress plugins in Bedrock projects often becomes error-prone when you mix theme vs project composer contexts, rely on ad-hoc CLI commands, or fail to register plugin packages correctly for Composer to fetch and WordPress to recognize.
Core Features & Use Cases
- Composer-only plugin installs in Bedrock: Uses lando composer require at the correct project-root composer.json to install plugins from WP Packagist sources.
- Handles multiple input formats: Accepts a plugin slug, a composer package name, or a local ZIP file (including mu-plugins) and wires repository metadata when needed.
- Optional activation verification: Can activate the plugin with lando wp plugin activate after installation, and always verifies via composer show and lando wp plugin list.
- Use case: You have a Bedrock project and need to install a new plugin from wp-packages.org (or a local ZIP you received from a vendor) and ensure it’s discoverable by WordPress without using wp plugin install.
Quick Start
Ask the skill to install the plugin inside your Lando Bedrock project using Composer: “Install-plugin for my Bedrock project from a ZIP at /path/to/my-plugin.zip and activate it after install.”