CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

browser-required

Use when auditing slow page loads, heavy assets, or rendering delays related to Perform browser-based performance audits. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

75%

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/browser-required/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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, concise overview that delegates executable detail appropriately to a real, one-level-deep reference file. Its main weakness is actionability within the body itself — guidance names tools and directions but no runnable commands, and the workflow lacks an explicit feedback loop.

Suggestions

Inline one minimal executable command in the Check or Fix section (e.g., a one-line Lighthouse CLI invocation) so the body is immediately actionable without opening the reference.

Remove the opening rationale sentence and the Quick Reference bullets that restate why browsers matter — Claude already knows this, and the reference's 'Why It Matters' section covers it.

Add an explicit validation checkpoint after Fix (e.g., 'Re-run the audit and confirm the targeted metric improved before considering the change done') to close the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is lean (~30 lines) with organized sections, but the opening rationale sentence ('Static analysis alone cannot simulate the complex rendering, script execution, and layout processes of modern web browsers') and the Quick Reference bullets restate knowledge Claude already has and could be trimmed.

4 / 5

Actionability

Specific tools (Lighthouse, Puppeteer, WebPageTest, DevTools) and metrics (LCP, CLS, INP) are named, and the Check/Fix sections give direction ('Ensure that performance audits are conducted in an environment that executes JavaScript and renders the page'), but the body contains no executable commands or code — the concrete examples are deferred to references/rule.md, leaving key details missing from the body itself.

3 / 5

Workflow Clarity

A coherent Check → Fix → Explain → Code Review sequence is present with most checkpoints included ('Ensure that performance audits are conducted in an environment that executes JavaScript', 'describe the measurement method used to confirm the issue'), though an explicit validate-and-retry feedback loop is absent.

4 / 5

Progressive Disclosure

A concise overview body clearly signals a one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'); the referenced file exists, contains substantial executable Lighthouse/Puppeteer content matching the pointer, and has no nested references.

5 / 5

Total

16

/

20

Passed

Description

70%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 solid description with explicit 'Use when' triggers, natural user phrasing, and specific tooling. Its main flaws are the grammatically garbled title splice ('related to Perform browser-based performance audits') and a thin set of concrete capability actions.

Suggestions

Fix the splice so the sentence reads naturally, e.g., 'Perform browser-based performance audits using Lighthouse, DevTools, or field data. Use when auditing slow page loads, heavy assets, or rendering delays — verify the actual bottleneck before recommending changes.'

Add 1-2 more concrete actions (e.g., 'run Lighthouse with CPU/network throttling, measure Core Web Vitals like LCP, CLS, and INP') to lift specificity.

Include common synonyms such as 'page speed' or 'Core Web Vitals' among the trigger terms to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain and 1-2 concrete actions ('Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes') but does not list several distinct capabilities, matching the 'domain plus 1-2 concrete actions' anchor rather than the 'several specific actions' anchor.

3 / 5

Completeness

Both what ('Perform browser-based performance audits', 'Verify the actual bottleneck in DevTools, Lighthouse, or field data') and when ('Use when auditing slow page loads, heavy assets, or rendering delays') are present; however, the garbled splice 'rendering delays related to Perform browser-based performance audits' keeps the what below the 'clearly and explicitly' bar of the top anchor.

4 / 5

Trigger Term Quality

Natural trigger phrases users would actually say are present ('auditing slow page loads, heavy assets, or rendering delays'), but common synonyms like 'page speed', 'site is slow', or 'Core Web Vitals' are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The niche tooling (DevTools, Lighthouse, field data) and distinct triggers make it mostly distinct from other skills, though 'heavy assets' could overlap with asset-optimization or bundling skills, so minor overlap risk remains.

4 / 5

Total

15

/

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/browser-required/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.