CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/lighthouse-budget-author

Drafts a `lighthouserc.js` (or `budget.json`) at design time - picks Web Vitals thresholds (LCP / INP / CLS) per route based on traffic class (cached / dynamic / API-heavy / form-heavy) and the team's NFRs, plus resource-size budgets (JS / CSS / images / total bytes). Emits the config file ready for the lighthouse-perf runner. Use when starting Lighthouse coverage on a project that has no budgets yet, or when the existing budgets need a redesign.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

100%

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

A high-quality, action-oriented skill body: concise reference tables, complete executable config examples, a sequenced six-step workflow with a validation feedback loop, and clean section organization. No bundle files are present or necessary.

DimensionReasoningScore

Conciseness

Lean and efficient — domain-specific reference tables (traffic-class thresholds, resource budgets, anti-patterns) carry information Claude does not already know, with no boilerplate explaining what Lighthouse or Web Vitals are; every section earns its place.

3 / 3

Actionability

Provides complete, copy-paste-ready `.lighthouserc.js` and `budget.json` artifacts plus executable bash validation commands, matching the 'fully executable, copy-paste ready' anchor; not below because the examples are concrete rather than pseudocode.

3 / 3

Workflow Clarity

Six clearly sequenced steps with an explicit validation checkpoint in Step 6 ('Validate the budget realistically') and a feedback loop (expect failures, categorize, relax), matching the top anchor for sequenced workflows with validation.

3 / 3

Progressive Disclosure

Well-organized self-contained single file with clearly labeled sections (Overview, When to use, Steps 1-6, Anti-patterns, References) and appropriately signaled external references one level deep; no bundle files are needed for this config-authoring skill.

3 / 3

Total

12

/

12

Passed

Description

100%

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

A strong, third-person description that names concrete actions, provides an explicit 'Use when' trigger, and carves out a distinct niche. It is concise yet specific with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Drafts a `lighthouserc.js`', 'picks Web Vitals thresholds (LCP / INP / CLS) per route', 'plus resource-size budgets (JS / CSS / images / total bytes)', 'Emits the config file' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (drafts config, picks thresholds/budgets, emits file) and when (explicit 'Use when...' clause with two triggers), matching the top anchor; not below because the trigger is explicit, not merely implied.

3 / 3

Trigger Term Quality

'Use when starting Lighthouse coverage on a project that has no budgets yet, or when the existing budgets need a redesign' uses natural terms (Lighthouse coverage, budgets, redesign) a user would actually say; not below because coverage is broad rather than missing common variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (Lighthouse budget authoring for the lighthouse-perf runner) with distinct, specific triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.

Reviewed

Table of Contents