CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

performance-budget

Use when reviewing CI configuration, bundle analysis workflows, or pull requests that add dependencies and assets. Distinguish bundle-size budgets from runtime budgets such as Lighthouse or Core Web Vitals so teams can enforce both.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/performance-budget/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 body is a well-structured review checklist with excellent progressive disclosure — a lean overview deferring implementation detail to a real, one-level-deep reference. Its weaknesses are a motivational intro paragraph that explains a concept Claude already knows, and actionability that names tools and files but includes no commands or threshold examples in the body itself.

Suggestions

Cut or compress the opening motivational paragraph to one sentence — the rationale for performance budgets is a concept Claude already knows, and the token budget is better spent on instructions.

Add one small executable anchor to the Fix section (e.g., a minimal size-limit config snippet or the Lighthouse CI assert command) so the body stands alone before jumping to references/rule.md.

De-duplicate the Quick Reference bullets against the Check/Fix/Explain/Code Review sections, and add a checkpoint distinguishing budgets that are merely defined from budgets actually enforced on pull requests.

DimensionReasoningScore

Conciseness

The opening paragraph ("Without automated enforcement, performance degrades gradually — each PR adds a small library... the app that loaded in 2 seconds now takes 5... far cheaper than debugging a slow production site") is motivational rationale for a concept Claude already knows, while the remaining sections are lean — matching anchor 3 (some unnecessary explanation) rather than anchor 4's minor instances.

3 / 5

Actionability

Concrete tool and file names are given ("size-limit", "Lighthouse CI assertions", "package.json", CI workflows) but the body contains no commands, config snippets, or example thresholds — all executable detail is deferred to references/rule.md. This fits anchor 3 (some concrete guidance but incomplete, missing key details) rather than anchor 4's mostly-executable guidance.

3 / 5

Workflow Clarity

A coherent Check → Fix → Explain → Code Review sequence suits this review skill, with no destructive or batch operations so no validation cap applies. It falls short of anchor 5 because the Quick Reference bullets partially duplicate the sections and there is no checkpoint distinguishing budgets that are defined from budgets actually enforced on PRs.

4 / 5

Progressive Disclosure

A lean ~33-line overview with a clearly signaled, one-level-deep pointer ("For full implementation details, code examples, and framework-specific guidance, see references/rule.md") to a verified 174-line reference containing real code examples — clean split and easy navigation matching anchor 5.

5 / 5

Total

15

/

20

Passed

Description

75%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.

A strong description with an explicit trigger clause, concrete review targets, and named tools/metrics in third-person voice. Its main gaps are the missing "performance budget" keyword (the term users would most naturally say) and a capability statement that is implied through the trigger and purpose clauses rather than stated up front.

DimensionReasoningScore

Specificity

Quotes several concrete actions with named targets — "reviewing CI configuration, bundle analysis workflows, or pull requests that add dependencies and assets" and "Distinguish bundle-size budgets from runtime budgets such as Lighthouse or Core Web Vitals" — but coverage has gaps (setup and RUM monitoring actions from the body are absent), matching anchor 4 rather than the comprehensive coverage of 5 or the 1-2 actions of 3.

4 / 5

Completeness

Explicit "Use when reviewing CI configuration... or pull requests that add dependencies and assets" answers when clearly, and the what ("Distinguish bundle-size budgets from runtime budgets... so teams can enforce both") is present but embedded in a purpose clause rather than a leading capability statement — anchor 4, not 5.

4 / 5

Trigger Term Quality

Good natural keyword coverage — "CI configuration", "pull requests", "dependencies", "Lighthouse", "Core Web Vitals" — but the most natural user phrase "performance budget" itself never appears, and synonyms like "bundle size" alone are missing, so it fits anchor 4 rather than comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (bundle-size vs runtime budgets, Lighthouse, Core Web Vitals) with mostly distinct triggers, but "reviewing CI configuration" is broad enough to overlap with generic CI-review skills — anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/performance-budget/SKILL.md

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.