laravel-plugin-discovery

Discover Laravel packages by feature and health status via LaraPlugins.io.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/cescrafli/compyrasion --skill laravel-plugin-discovery-cescrafli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: laravel-plugin-discovery
Source: https://github.com/cescrafli/compyrasion/tree/main/skills/laravel-plugin-discovery
Command: npx skills add https://github.com/cescrafli/compyrasion --skill laravel-plugin-discovery-cescrafli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discover and evaluate Laravel packages via the LaraPlugins.io MCP server, streamlining decision-making.

Core Features & Use Cases

  • Discover packages by feature keywords and health status
  • Check Laravel/PHP compatibility and maintenance status
  • Review detailed package metrics and vendor information

Quick Start

Ask the assistant to search for Laravel authentication packages with Healthy status using the MCP, then review top results and their details.

Frequently Asked Questions about laravel-plugin-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find healthy Laravel packages for a specific feature?

You can discover healthy Laravel packages by searching feature keywords via the LaraPlugins.io MCP server, which filters results by stability and maintenance status, returning package names, health metrics, and vendor reputation.

What is the best way to check Laravel and PHP compatibility for a plugin?

Evaluate Laravel and PHP compatibility by assessing plugin metrics across relevant framework versions, verifying package maintenance status, compatibility notes, and vendor reputation via the MCP server.

Can I evaluate vendor reputation and package health before adding a Laravel plugin?

Yes, you can evaluate Laravel plugin vendor reputation and package health by reviewing detailed package metrics, maintenance status, and compatibility notes surfaced through the MCP server.

Does the laravel-plugin-discovery MCP server work without additional dependencies?

The laravel-plugin-discovery MCP server operates with zero dependencies, directly querying Laravel package health and compatibility metrics, enabling immediate feature discovery and stability assessment without external setup.

What limitations exist when discovering Laravel packages through an MCP server?

Limitations of discovering Laravel packages via an MCP server include reliance on surfaced structured metrics like health status, compatibility notes, and vendor reputation, without performing deep code-level analysis.