performance-lighthouse-runner
Performance Lighthouse Runner - Auto-activating skill for Frontend Development. Triggers on: performance lighthouse runner, performance lighthouse runner Part of the Frontend Development skill category.
36
3%
Does it follow best practices?
Impact
96%
1.12xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/05-frontend-dev/performance-lighthouse-runner/SKILL.mdQuality
Discovery
7%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 essentially just the skill's name repeated with boilerplate category metadata. It provides no concrete actions, no explicit trigger guidance, and no natural keywords a user would use. It would be nearly impossible for Claude to reliably select this skill from a pool of similar frontend development skills.
Suggestions
Add concrete actions the skill performs, e.g., 'Runs Google Lighthouse audits, measures Core Web Vitals, generates performance scores and optimization recommendations.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about page speed, Lighthouse scores, web performance audits, load time optimization, or Core Web Vitals.'
Remove the duplicated trigger term and expand with varied natural keywords users would actually say, such as 'performance audit', 'site speed', 'accessibility score', 'SEO audit', 'PWA check'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names no concrete actions. It only states it is a 'Performance Lighthouse Runner' and an 'auto-activating skill for Frontend Development' without describing what it actually does (e.g., runs Lighthouse audits, generates performance reports, analyzes Core Web Vitals). | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause and no description of capabilities beyond the skill's name. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'performance lighthouse runner' repeated twice. It misses natural user phrases like 'page speed', 'web performance audit', 'Core Web Vitals', 'Lighthouse score', 'site performance', or 'load time'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Lighthouse' does narrow the domain somewhat compared to a fully generic description, but without specific actions or triggers it could still overlap with general frontend performance or testing skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template/placeholder with no substantive content. It contains no actionable instructions for running Lighthouse, no CLI commands (e.g., `npx lighthouse`), no code examples, no interpretation guidance for scores, and no real workflow. Every section is generic boilerplate that could apply to any skill by swapping the name.
Suggestions
Add concrete, executable commands for running Lighthouse (e.g., `npx lighthouse https://example.com --output=json --output-path=./report.json`) and programmatic usage via the Node API.
Include a clear workflow: 1) Run audit, 2) Parse results, 3) Identify failing metrics against thresholds, 4) Apply specific fixes, 5) Re-run to validate improvements.
Provide specific guidance on interpreting key metrics (LCP, FID/INP, CLS, FCP, TTFB) with actionable fix patterns for common issues like render-blocking resources, unoptimized images, and layout shifts.
Remove all generic boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that provide no actionable information and replace with concrete reference material.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the phrase 'performance lighthouse runner' excessively, and provides zero substantive information about actually running Lighthouse or interpreting results. | 1 / 3 |
Actionability | There are no concrete commands, code snippets, CLI invocations, or specific instructions. The skill describes what it could do in abstract terms ('provides step-by-step guidance') without actually providing any guidance whatsoever. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The content merely lists vague capabilities like 'validates outputs against common standards' without specifying how. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to supporting files, no structured navigation, and no meaningful organization of content across sections. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
13d35b8
- 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.