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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill performance-lighthouse-runnerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It names the tool but fails to describe what actions it performs, what outputs it produces, or when Claude should select it. The redundant trigger terms and lack of natural user keywords make it unlikely to be selected appropriately.
Suggestions
Add specific actions the skill performs, e.g., 'Runs Google Lighthouse audits to measure page performance, accessibility, SEO, and best practices. Generates performance scores and actionable recommendations.'
Include a 'Use when...' clause with natural trigger terms like 'page speed', 'performance audit', 'Core Web Vitals', 'lighthouse score', 'site performance', 'load time optimization'
Remove the redundant trigger term and replace with varied natural language users would actually say when needing performance analysis
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Performance Lighthouse Runner') without describing any concrete actions. There's no indication of what it actually does - no verbs like 'analyzes', 'measures', 'generates reports', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than describing actual use cases. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('performance lighthouse runner' repeated twice) and overly specific. Missing natural user terms like 'page speed', 'web performance', 'site audit', 'Core Web Vitals', 'load time', or 'performance metrics'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Lighthouse' provides some specificity to Google's Lighthouse tool, but 'Frontend Development' category is broad. Without describing specific capabilities, it could conflict with other performance or frontend skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is an empty template that provides zero actionable information about running Lighthouse performance audits. It contains only generic placeholder text that could apply to any skill, with no actual commands, code examples, metric explanations, or workflows for performance testing.
Suggestions
Add executable examples showing how to run Lighthouse (e.g., `npx lighthouse https://example.com --output=json --output-path=./report.json`)
Include a workflow for interpreting Lighthouse scores with specific thresholds and remediation steps for common issues
Provide concrete guidance on key metrics (LCP, FID, CLS) with target values and optimization techniques
Remove all generic boilerplate text and replace with Lighthouse-specific instructions and examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about Lighthouse or performance testing. Every section describes what the skill does abstractly rather than providing concrete guidance. | 1 / 3 |
Actionability | No executable code, commands, or specific instructions are provided. The content only describes vague capabilities like 'provides step-by-step guidance' without actually providing any guidance on running Lighthouse or interpreting results. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for running Lighthouse, no validation checkpoints, and no process for analyzing or acting on performance metrics. | 1 / 3 |
Progressive Disclosure | The content is a flat, generic template with no meaningful structure. There are no references to detailed documentation, no examples, and no organization of content by complexity or use case. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.