CtrlK
BlogDocsLog inGet started
Tessl Logo

livewire-development

Vendor-overridden Livewire skill

44

1.00x
Quality

13%

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/Fixtures/vendor-skills/livewire-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

18%Weight 40%Scale 1-5

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

The content body is effectively a placeholder — a heading plus a single meta sentence about overriding a built-in skill. It provides no actionable guidance, no workflow, and no referenced materials for Livewire development.

Suggestions

Add concrete, executable guidance for the core Livewire task (e.g. creating a component, defining wire:model bindings, rendering views).

Provide a clear workflow with validation for any destructive or batch Livewire operations (e.g. testing components after edits).

Either populate the body with real instructions or move detail into reference files and link them one level deep from the overview.

DimensionReasoningScore

Conciseness

The body is lean and not padded, but the single sentence ("This skill was discovered from a vendor package...") is meta-commentary unrelated to the task rather than efficient skill content, so it does not fully earn its tokens.

3 / 5

Actionability

No concrete code, commands, or specific guidance appears; the body only makes a meta statement about overriding a built-in version rather than instructing how to develop with Livewire.

1 / 5

Workflow Clarity

There is no sequence of steps and no validation checkpoints; the body contains no actual workflow content at all.

1 / 5

Progressive Disclosure

The body is a minimal stub with one heading and one sentence, no references, and no real organization of content; it does not meet the well-organized-sections bar for the simple-skill exception.

2 / 5

Total

7

/

20

Passed

Description

7%Weight 40%Scale 1-5

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

This description is a bare stub that identifies the domain (Livewire) but describes no capabilities and gives no trigger guidance. It reads as packaging metadata rather than a usable skill description.

Suggestions

Replace the description with concrete actions, e.g. 'Build Livewire components, handle wire:model bindings, and debug Livewire requests in Laravel.'

Add an explicit 'Use when...' clause naming natural user triggers such as 'Livewire components', 'wire:model', or 'Laravel Livewire'.

Clarify distinctiveness so it does not appear to merely duplicate the built-in Livewire skill being overridden.

DimensionReasoningScore

Specificity

The phrase "Vendor-overridden Livewire skill" names the Livewire domain but provides no concrete actions whatsoever; unlike the score-2 anchor ("Processes PDF files"), it lacks even a minimal action verb.

1 / 5

Completeness

Neither "what does this do" (no actions) nor "when should Claude use it" (no Use-when clause) is present; both are extremely vague, matching the lowest anchor.

1 / 5

Trigger Term Quality

"Vendor-overridden" is packaging/infrastructure jargon and "Livewire" is technical framework terminology; no natural phrases a user would actually say when needing this skill appear.

1 / 5

Distinctiveness Conflict Risk

"Livewire" names a specific niche with distinct triggers, but the description is vague and explicitly conflicts with a built-in .ai/ Livewire skill, leaving moderate overlap risk.

3 / 5

Total

6

/

20

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.