CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

defer-async

Use when reviewing templates, rendered HTML, or shared components related to Load scripts with defer, async, or type=module. Validate the final browser-facing markup, not just the source framework abstraction.

Quality

79%

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/defer-async/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A lean, well-structured review skill with an unambiguous check procedure, concrete fix guidance, and an exemplary one-level reference to a real bundle file. Its only real cost is the opening background paragraph and Quick Reference restating script-loading concepts Claude already knows, which could be trimmed without losing anything actionable.

Suggestions

Trim or cut the intro paragraph about parser blocking and white-screen time — Claude already knows why blocking scripts hurt rendering; the Quick Reference bullets carry the needed semantics in fewer tokens.

Add one tiny before/after markup pair (e.g. '<script src="app.js"></script>' → '<script src="app.js" defer></script>') in the Fix section to make the guidance copy-paste ready and lift actionability to the top anchor.

Consider dropping the 'Explain' section's restatement of the difference between defer, async, and type=module, or compressing it to a pointer into the Quick Reference, since that ground is already covered twice in the body.

DimensionReasoningScore

Conciseness

The opening paragraph ('A plain <script> tag in the document head blocks all HTML parsing... On a slow network this can add seconds of white-screen time... reducing Time to First Contentful Paint dramatically') explains parser-blocking behavior Claude already knows, and the Quick Reference bullets restate the standard defer/async/type=module semantics. This is unnecessary explanation beyond minor trimming (below the 4 anchor) but the sections are compact with no real padding (above the 2 anchor).

3 / 5

Actionability

The Check and Fix sections give concrete, executable criteria: 'Find all script tags in this HTML file. Flag any in the <head> without defer or async, and any at the bottom of <body> that could be in <head> with defer' and 'Add defer or async to script tags in the document head, or convert to type=module'. This is specific, unambiguous instruction-guidance rather than pseudocode (above the 3 anchor), but no before/after markup example appears in the body — examples are deferred to the reference file — so it is not fully copy-paste ready (below the 5 anchor).

4 / 5

Workflow Clarity

This is a simple, single-purpose review skill (under 50 lines), and the single action is unambiguous: the Check section gives exact flagging criteria (head without defer/async; bottom-of-body that could move to head with defer), followed by a coherent Fix → Explain → Code Review progression. Per the simple-skill guideline this earns a 5; the destructive/batch validation cap does not apply since the operation only flags and suggests markup changes.

5 / 5

Progressive Disclosure

The body is well-organized into Quick Reference / Check / Fix / Explain / Code Review sections and ends with a single, clearly-signaled, one-level-deep reference — 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — and that file verifiedly exists in the bundle. This matches the clear-overview anchor with appropriate content split and easy navigation.

5 / 5

Total

17

/

20

Passed

Description

73%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 well-targeted description with an explicit 'Use when' trigger, concrete domain keywords, and a distinctive niche around defer/async/type=module script loading in rendered HTML. Its main weakness is that the capability side names only review-and-validate actions without stating the concrete flag/fix outcomes, leaving it slightly under-specified.

Suggestions

State the concrete outcome actions, e.g. 'Flag scripts in <head> without defer or async, flag bottom-of-body scripts that could move to <head> with defer, and apply the fixes' — this would lift specificity and completeness to the top anchors.

Add one or two natural synonym trigger phrases such as 'script loading', 'blocking scripts', or 'page rendering performance' so users phrasing the need differently still match.

Keep the third-person imperative voice as-is ('Validate...') — it already satisfies the voice guideline; just avoid drifting into 'You can use...' phrasing when editing.

DimensionReasoningScore

Specificity

The description names its domain precisely ('related to Load scripts with defer, async, or type=module') and gives 1-2 concrete actions ('reviewing templates, rendered HTML, or shared components', 'Validate the final browser-facing markup, not just the source framework abstraction'), matching the anchor for a named domain with 1-2 concrete but not comprehensive actions. It does not list several distinct actions needed for a 4, and its actions are far more concrete than the generic minimal phrasing of a 2.

3 / 5

Completeness

Both parts are explicitly present: 'when' via 'Use when reviewing templates, rendered HTML, or shared components related to Load scripts...' and 'what' via 'Validate the final browser-facing markup, not just the source framework abstraction'. This matches the anchor where both exist but could be more explicit — the 'what' stops short of stating the concrete outcome (flagging scripts that lack defer/async), which keeps it from a 5, while clearly exceeding the missing-or-weak-when level of a 3.

4 / 5

Trigger Term Quality

Natural keywords a user would say are present: 'templates', 'rendered HTML', 'shared components', 'defer', 'async', 'type=module', plus 'browser-facing markup'. It falls short of the comprehensive anchor (5) because common variations like 'script loading', 'blocking scripts', or 'rendering performance' are missing, but it goes well beyond the sparse keyword coverage of a 3.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — script loading attributes (defer/async/type=module) in final rendered markup — with distinct trigger terms unlikely to fire for unrelated skills. This matches the minimal-conflict-risk anchor exactly; no neighboring anchor fits better.

5 / 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/defer-async/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.