CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

javascript-inline

Use when reviewing scripts, client components, bundles, or runtime behavior related to Avoid inline JavaScript. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.

Quality

72%

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/javascript-inline/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, token-efficient overview that delegates depth correctly to a single real reference file, with a clear Check/Fix/Explain/Code Review sequence. Its main weakness is actionability: beyond the Quick Reference bullets, the guidance stays abstract with no executable example or concrete verification step in the body itself.

Suggestions

Add a minimal before/after snippet to the Fix section (inline `onclick="..."` attribute vs. `addEventListener` in an external file) so the core fix is executable without opening the reference.

Replace the vague 'use modern JavaScript patterns for DOM interaction' with named techniques, e.g. event delegation or data attributes for passing state to handlers.

Make Code Review's verification concrete — e.g. check the Network panel for the cached external script and confirm no CSP violations in the console — instead of just directing to 'state how the change should be verified'.

DimensionReasoningScore

Conciseness

The ~35-line body is lean overall — the Quick Reference bullets ('Move onclick/onmouseover handlers to external JS files', 'Use addEventListener instead of inline event handlers') earn their tokens — but the intro sentence explains caching/CSP consequences Claude already knows, and the Check section ('Verify that JavaScript code is not mixed with HTML markup using external script files and proper separation of concerns for better maintainability and performance') is circular and redundant with the intro, marking minor over-explanation to trim (anchor 4, not 5).

4 / 5

Actionability

Some concrete guidance exists ('Use addEventListener instead of inline event handlers', 'Exception: critical above-the-fold JS can be inlined'), but the body contains no executable code and its Fix/Check sections are abstract ('use modern JavaScript patterns for DOM interaction'), leaving key implementation details entirely deferred to the reference file — matching anchor 3's 'some concrete guidance but incomplete' rather than anchor 4's mostly-executable bar.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a clear, labeled sequence for this simple single-purpose skill, and Code Review explicitly instructs to 'state how the change should be verified in the browser' — a verification directive is present, but no concrete validation steps or feedback loop (verify → fix → retry) are given in the body, placing it at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The body is a concise overview with one clearly signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), and that file exists and delivers exactly the promised content (code examples, React/Vue/Angular guidance, verification steps) with no nested references — matching the anchor-5 pattern of a well-organized overview pointing to appropriately split detail.

5 / 5

Total

16

/

20

Passed

Description

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

The description has an explicit and well-formed 'Use when' trigger and a distinguishable niche, but its capability statement relies on generic inspection verbs and omits the concrete actions the skill performs and common natural trigger phrases like 'inline event handlers' or 'onclick'. It sits comfortably at the midpoint-plus of the rubric: clear intent, moderate specificity.

Suggestions

State concrete capabilities instead of generic inspection verbs, e.g. 'Move inline onclick/onmouseover handlers to external files, replace them with addEventListener, and check CSP compliance.'

Add the natural trigger phrases users would actually say — 'inline event handlers', 'onclick attributes', 'script tags in HTML', 'CSP violations' — alongside 'inline JavaScript'.

Trim the broad opening list ('scripts, client components, bundles, or runtime behavior') to the contexts where inline-JS issues actually arise, reducing overlap with general JavaScript review skills.

DimensionReasoningScore

Specificity

The description names its domain ("related to Avoid inline JavaScript") and a couple of actions ("reviewing scripts, client components, bundles, or runtime behavior"; "Inspect both source code and the browser execution path"), but the actions are generic inspection verbs with no concrete remediation steps (e.g., moving handlers to external files or using addEventListener), so it matches anchor 3 rather than the several-specific-actions bar of anchor 4.

3 / 5

Completeness

It explicitly answers when ("Use when reviewing scripts, client components, bundles, or runtime behavior related to Avoid inline JavaScript") and states a what ("Inspect both source code and the browser execution path so fixes target the real bottleneck or bug"), but the what is generic inspection language without the concrete action phrases of the anchor-5 example, so anchor 4 is the best fit.

4 / 5

Trigger Term Quality

It includes relevant keywords ("scripts", "client components", "bundles", "runtime behavior", "inline JavaScript") but misses common variations users would naturally say such as "inline event handlers", "onclick", or "script tags", and the phrase "related to Avoid inline JavaScript" is rule-name phrasing rather than natural speech — fitting anchor 3, not the good-coverage bar of anchor 4.

3 / 5

Distinctiveness Conflict Risk

The qualifier "related to Avoid inline JavaScript" carves a clear niche, but the broad opening list ("scripts, client components, bundles, or runtime behavior") overlaps general JavaScript/frontend review skills, leaving minor conflict risk with closely related skills rather than the minimal risk of anchor 5.

4 / 5

Total

14

/

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/javascript-inline/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.