Agent skill · data analytics · affaan-m

laravel-plugin-discovery

Discover and evaluate Laravel packages via LaraPlugins.io MCP. Use when the user wants to find plugins, check package health, or assess Laravel/PHP compatibility.

Why this skill is useful

Provides specific commands and filters for evaluating Laravel packages that the AI wouldn't reliably generate on its own.

What it needs

About 4k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.

What this skill does

Laravel Plugin Discovery Find, evaluate, and choose healthy Laravel packages using the LaraPlugins.io MCP server. When to Use User wants to find Laravel packages for a specific feature (e.g. "auth", "permissions", "admin panel") User asks "what package should I use for..." or "is there a Laravel package for..." User wants to check if a package is actively maintained User needs to verify Laravel version compatibility User wants to assess package health before adding to a project MCP Requirement LaraPlugins MCP server must be configured. Add to your ~/.claude.json mcpServers: No API key required — the server is free for the Laravel community. MCP Tools The LaraPlugins MCP provides two primary tools: SearchPluginTool Search packages by keyword, health score, vendor, and version compatibility. Parameters: textsearch (string, optional): Keyword to search (e.g. "permission", "admin", "api") healthscore (string, optional): Filter by health band — Healthy, Medium, Unhealthy, or Unrated laravelcompatibility (string, optional): Filter by Laravel version — "5", "6", "7", "8", "9", "10", "11", "12", "13" phpcompatibility (string, optional): Filter by PHP version — "7.4", "8.0", "8.1", "8.2", "8.3", "8.4", "8.5" vendorfilter (string, optional): Filter by vendor name (e.g. "spatie", "laravel") page (number, optional): Page number for pagination GetPluginDetailsTool Fetch detailed metrics, readme content, and version history for a specific package. Parameters: package (string, required): Full Composer package name (e.g. "spatie/laravel-permission") includeversions (boolean, optional): Include version history in response --- How It Works Finding Packages When the user wants to discover packages for a feature: 1. Use SearchPluginTool with relevant keywords 2. Apply filters for health score, Laravel version, or PHP version 3. Review the results with package names, descriptions, and health indicators Evaluating Packages When the user wants to assess a specific package: 1. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills affaan-m/laravel-plugin-discovery--4f66a6

View the source on GitHub

Browse the @skills marketplace