CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/laravel-plugin-discovery/SKILL.md

The canonical home for this skill is tdg-personal/laravel-plugin-discovery

SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete tool calls and parameters, but it is verbose due to duplicated content across sections and ships as a monolithic single file with no progressive disclosure. Workflows are sequenced but lack explicit validation checkpoints.

Suggestions

De-duplicate the filter values: the health bands and Laravel/PHP versions appear in both the MCP Tools parameter list and the Best Practices tables — keep one canonical source and reference it.

Move the parameter reference, Response Interpretation, and Common Use Cases tables into a bundled references/ file so SKILL.md stays a lean overview with one-level-deep links.

Add an explicit validation step in the Evaluating Packages workflow (e.g. confirm the returned health score and last-activity date before recommending a package).

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining concepts Claude already knows, but the filter values and use cases are restated across the MCP Tools, tables, and Best Practices sections, so it could be tightened by removing the duplication.

2 / 3

Actionability

It provides concrete tool names, typed parameter lists, and multiple copy-paste-ready example calls like SearchPluginTool({text_search: "authentication", health_score: "Healthy"}), giving fully executable guidance.

3 / 3

Workflow Clarity

Finding/Evaluating/Checking workflows are given as numbered sequences, but there are no validation checkpoints or quality checks on results, and the sequence relies on implicit review rather than explicit feedback loops.

2 / 3

Progressive Disclosure

Content is well-organized into headed sections but everything lives inline in a single ~225-line SKILL.md with no bundle files; the parameter reference, response-interpretation, and use-case material that could be split out is kept inline.

2 / 3

Total

9

/

12

Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, well-formed description that clearly answers what and when with explicit triggers and a distinct Laravel-specific niche. The only soft spot is specificity, which names the domain and a couple of actions rather than a comprehensive list of concrete operations.

DimensionReasoningScore

Specificity

"Discover and evaluate Laravel packages via LaraPlugins.io MCP" names the domain and two actions (discover, evaluate) but does not enumerate multiple granular concrete actions, so it stops short of the comprehensive list anchor.

2 / 3

Completeness

It states what it does ("Discover and evaluate Laravel packages via LaraPlugins.io MCP") and gives an explicit "Use when" clause covering when to invoke it, answering both what and when.

3 / 3

Trigger Term Quality

"find plugins, check package health, assess Laravel/PHP compatibility" are natural phrases a user would say, giving good coverage of trigger terms for this niche.

3 / 3

Distinctiveness Conflict Risk

The LaraPlugins.io MCP / Laravel-package niche with Laravel-specific triggers is clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.