affaan-m/ecc

laravel-plugin-discovery

Discover and evaluate Laravel packages via LaraPlugins.io MCP.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/affaan-m/ecc --skill laravel-plugin-discovery

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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:

json
"laraplugins": {
  "type": "http",
  "url": "https://laraplugins.io/mcp/plugins"
}

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:

  • text_search (string, optional): Keyword to search (e.g. "permission", "admin", "api")
  • health_score (string, optional): Filter by health band — Healthy, Medium, Unhealthy, or Unrated
  • laravel_compatibility (string, optional): Filter by Laravel version — "5", "6", "7", "8", "9", "10", "11", "12", "13"
  • php_compatibility (string, optional): Filter by PHP version — "7.4", "8.0", "8.1", "8.2", "8.3", "8.4", "8.5"
  • vendor_filter (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")
  • include_versions (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. Use GetPluginDetailsTool with the package name
  2. Review health score, last updated date, Laravel version support
  3. Check vendor reputation and risk indicators

Checking Compatibility

When the user needs Laravel or PHP version compatibility:

  1. Search with laravel_compatibility filter set to their version
  2. Or get details on a specific package to see its supported versions

Examples

Example: Find Authentication Packages

SearchPluginTool({
  text_search: "authentication",
  health_score: "Healthy"
})

Returns packages matching "authentication" with healthy status:

  • spatie/laravel-permission
  • laravel/breeze
  • laravel/passport
  • etc.

Example: Find Laravel 12 Compatible Packages

SearchPluginTool({
  text_search: "admin panel",
  laravel_compatibility: "12"
})

Returns packages compatible with Laravel 12.

Example: Get Package Details

GetPluginDetailsTool({
  package: "spatie/laravel-permission",
  include_versions: true
})

Returns:

  • Health score and last activity
  • Laravel/PHP version support
  • Vendor reputation (risk score)
  • Version history
  • Brief description

Example: Find Packages by Vendor

SearchPluginTool({
  vendor_filter: "spatie",
  health_score: "Healthy"
})

Returns all healthy packages from vendor "spatie".


Filtering Best Practices

By Health Score

Health BandMeaning
HealthyActive maintenance, recent updates
MediumOccasional updates, may need attention
UnhealthyAbandoned or infrequently maintained
UnratedNot yet assessed

Recommendation: Prefer Healthy packages for production applications.

By Laravel Version

VersionNotes
13Latest Laravel
12Current stable
11Still widely used
10Legacy but common
5-9Deprecated

Recommendation: Match the target project's Laravel version.

Combining Filters

typescript
// Find healthy, Laravel 12 compatible packages for permissions
SearchPluginTool({
  text_search: "permission",
  health_score: "Healthy",
  laravel_compatibility: "12"
})

Response Interpretation

Search Results

Each result includes:

  • Package name (e.g. spatie/laravel-permission)
  • Brief description
  • Health status indicator
  • Laravel version support badges

Package Details

The detailed response includes:

  • Health Score: Numeric or band indicator
  • Last Activity: When the package was last updated
  • Laravel Support: Version compatibility matrix
  • PHP Support: PHP version compatibility
  • Risk Score: Vendor trust indicators
  • Version History: Recent release timeline

Common Use Cases

ScenarioRecommended Approach
"What package for auth?"Search "auth" with healthy filter
"Is spatie/package still maintained?"Get details, check health score
"Need Laravel 12 packages"Search with laravel_compatibility: "12"
"Find admin panel packages"Search "admin panel", review results
"Check vendor reputation"Search by vendor, check details

Best Practices

  1. Always filter by health — Use health_score: "Healthy" for production projects
  2. Match Laravel version — Always check laravel_compatibility matches the target project
  3. Check vendor reputation — Prefer packages from known vendors (spatie, laravel, etc.)
  4. Review before recommending — Use GetPluginDetailsTool for a comprehensive assessment
  5. No API key needed — The MCP is free, no authentication required

Related Skills

  • laravel-patterns — Laravel architecture and patterns
  • laravel-tdd — Test-driven development for Laravel
  • laravel-security — Laravel security best practices
  • documentation-lookup — General library documentation lookup (Context7)

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
affaan-m
커뮤니티

rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology. Use when writing Rust tests — unit, integration, async, property-based, or coverage.

24시간 설치 수
489
GitHub Stars
30.8만
업데이트
11월 20일
affaan-m
커뮤니티

search-first

Research-before-coding workflow: search npm/PyPI, MCP servers, skills, and GitHub for existing tools before writing custom code, then adopt, extend, or build. Launches the researcher agent for non-trivial needs. Use when starting a feature, adding a dependency or integration, or about to write a utility that may already exist.

1시간 설치 수
5
GitHub Stars
30.8만
업데이트
11월 20일
affaan-m
커뮤니티

browser-qa

Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.

1시간 설치 수
2
GitHub Stars
30.8만
업데이트
11월 20일
affaan-m
커뮤니티

docker-patterns

Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation.

1시간 설치 수
2
GitHub Stars
30.8만
업데이트
11월 20일