CtrlK
BlogDocsLog inGet started
Tessl Logo

livewire-development

Vendor-overridden Livewire skill

50

1.00x
Quality

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

22%

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

The body is essentially empty of skill content: a heading plus one administrative sentence about discovery and override precedence, with no actionable guidance, examples, or workflow. It is concise only because it contains almost nothing usable.

Suggestions

Add concrete, executable guidance for Livewire tasks (e.g., component scaffolding commands, form-action wiring, and lifecycle debugging examples) so the body instructs rather than describes.

Provide at least a minimal workflow or ordered steps for the most common Livewire operation, including any validation/verification step if changes are destructive or batch-oriented.

Restructure into a brief overview with well-organized sections (Quick start, Common tasks) and, as the skill grows, signal one-level-deep reference files under references/ rather than relying on a single provenance line.

DimensionReasoningScore

Conciseness

The body is maximally brief and free of verbosity, but the single sentence ("This skill was discovered from a vendor package and should override the built-in .ai/ version") is administrative context that does not advance any capability, so it does not reach "every token earns its place."

2 / 3

Actionability

There is no concrete guidance, code, or commands for working with Livewire; the body merely describes provenance, matching "describes rather than instructs."

1 / 3

Workflow Clarity

No steps or sequence are provided at all, and the simple-skill carve-out requires an unambiguous single action; here no action is defined, so it cannot reach 2 or 3.

1 / 3

Progressive Disclosure

It avoids gross failures (no monolithic wall, no nested references, and no bundle files exist to mis-signal), lifting it above 1, but a one-line admin note is not the clear, well-organized overview the simple-skill note rewards with a 3.

2 / 3

Total

6

/

12

Passed

Description

22%

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

The description is administrative meta-text rather than a functional skill description: it labels the skill's provenance/precedence but states no concrete actions, no usage triggers, and no clear differentiation. It fails to answer either what the skill does or when to invoke it.

Suggestions

Replace the description with concrete Livewire actions (e.g., 'Creates and refactors Livewire components, wires form actions, and debugs Livewire lifecycle issues') instead of the administrative 'Vendor-overridden Livewire skill' phrasing.

Add an explicit trigger clause such as 'Use when working with Laravel Livewire components, wireables, or full-page components' so both the 'what' and the 'when' are answered.

Clarify distinctiveness by naming Livewire-specific triggers (components, mount/render lifecycle, Alpine integration) rather than the generic 'vendor override' framing that invites overlap with the built-in version.

DimensionReasoningScore

Specificity

The phrase "Vendor-overridden Livewire skill" names a domain (Livewire) but states zero concrete actions; anchor 2 requires "some actions," and none are present, so it stays at the vague/abstract level.

1 / 3

Completeness

The description only weakly implies "what" (an administrative classification, not capabilities) and entirely omits "when" to use it; with "when" missing and "what" very weak, it matches "Missing what OR when, or both very weak."

1 / 3

Trigger Term Quality

"Livewire" is one natural keyword a Laravel user would actually say, but it lacks common variations and any explicit trigger phrasing, fitting "some relevant keywords but missing common variations"; not a 1 because the term is genuine, not a 3 because coverage is thin and no triggers are given.

2 / 3

Distinctiveness Conflict Risk

"Livewire" is a specific niche unlikely to clash with unrelated skills, but "Vendor-overridden" signals it is a variant meant to replace a built-in version, so it could overlap with a similar skill.

2 / 3

Total

6

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
laravel/boost
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.