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 a title repeated as trigger terms with boilerplate category metadata. It fails to describe any concrete capabilities, lacks natural user-facing keywords, and provides no guidance on when Claude should select this skill. It would be nearly indistinguishable from any other performance-related frontend skill.
Suggestions
Add concrete actions the skill performs, e.g., 'Runs Google Lighthouse audits to measure page load speed, accessibility scores, SEO compliance, and Core Web Vitals metrics.'
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, Core Web Vitals, or site optimization.'
Expand trigger terms to include natural variations users would say: 'Lighthouse audit', 'page speed', 'performance score', 'Core Web Vitals', 'web performance', 'site speed test'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names no concrete actions. It only states 'Performance Lighthouse Runner' and 'Auto-activating skill for Frontend Development' without describing what it actually does (e.g., runs Lighthouse audits, generates performance reports, analyzes page speed metrics). | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no explanation of capabilities and no explicit 'Use when...' clause with trigger guidance. | 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', 'Lighthouse score', 'Core Web Vitals', 'performance metrics', or 'site speed'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Lighthouse' provides some specificity that distinguishes it from generic frontend or performance skills, but the lack of concrete actions and the broad 'Frontend Development' category label could cause overlap with other frontend performance-related 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 shell with no substantive content. It contains only auto-generated boilerplate that repeats the skill name without providing any actual instructions, commands, code examples, or guidance for running Lighthouse performance audits. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable commands for running Lighthouse (e.g., `npx lighthouse https://example.com --output=json --output-path=./report.json`) with key CLI flags explained.
Include a clear workflow: 1) Run audit, 2) Parse results for key metrics (LCP, FID, CLS, etc.), 3) Identify failing audits, 4) Provide fix recommendations, with validation checkpoints.
Add example output showing how to interpret Lighthouse JSON results and what score thresholds to target (e.g., performance >= 90).
Remove all generic boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actionable content about Lighthouse configuration, CI integration, and common performance fixes.
| 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, configurations, or executable guidance whatsoever. The skill describes what it could do in abstract terms ('provides step-by-step guidance') without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. Running Lighthouse audits is inherently a multi-step process (install, configure, run, interpret results, fix issues) and none of this is addressed. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative document with no meaningful structure. There are no references to detailed guides, no links to configuration examples, and the sections that exist contain only generic placeholder text. | 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
3e83543
- 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.