scheduler-yield

Use when reviewing JavaScript that performs synchronous loops over large datasets, recursive tree traversals, or bulk DOM updates that may exceed 50 ms on mid-range devices.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/scheduler-yield/SKILL.md

Quality

Content

72%

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

A well-structured, concise overview that practices clean progressive disclosure by deferring detail to rule.md. Its weaknesses are that the body carries no executable code and no inline validation checkpoints, both of which are pushed into the reference.

Suggestions

Include one small inline code snippet (a minimal yieldToMain + processInChunks usage) so the body is actionable without opening the reference.

Add a brief inline verification checkpoint (e.g. 'Confirm via the Performance panel that no Long Task exceeds 50 ms') so the review workflow has an explicit validation step in the body itself.

Dimension	Reasoning	Score
Conciseness	The body is lean — a short intro, a compact Quick Reference, and one-line Check/Fix/Explain/Code Review directives — with full detail deferred to the reference. Every section earns its place and it assumes Claude's competence. Not a 2 because it avoids padding and explanatory fluff.	3 / 3
Actionability	The directives name concrete tools ('scheduler.yield() with a MessageChannel fallback', 'exceed 50 ms') but the body contains no executable code — all runnable examples live in references/rule.md. Matches the anchor for concrete-but-incomplete guidance missing key inline details. Not a 3 because nothing in the body is copy-paste ready.	2 / 3
Workflow Clarity	Check, Fix, Explain, and Code Review form a loose review sequence, but there are no validation or verification checkpoints in the body (those live in the reference's Verification section). Not a 3 because validation gaps cap it; not a 1 because the phases are clearly listed and ordered.	2 / 3
Progressive Disclosure	The body is an overview that explicitly signals a single one-level-deep reference ('see references/rule.md'), which exists on disk, with content appropriately split. Matches the anchor for clear overview with well-signaled one-level references.	3 / 3
	Total	10 / 12 Passed

Description

82%

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 specific, well-triggered description targeting a distinct JS performance niche, with a clear 'Use when' clause. Its main gap is that it states the detection trigger but not the skill's actual remediation action.

Suggestions

Add an explicit 'what' clause naming the action, e.g. 'Refactors long synchronous tasks to yield to the main thread using scheduler.yield() with a MessageChannel fallback.'

Soften 'may exceed 50 ms on mid-range devices' into more natural user phrasing like 'loops that freeze the page' alongside the technical threshold.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete patterns — 'synchronous loops over large datasets, recursive tree traversals, or bulk DOM updates' — plus a quantified '50 ms on mid-range devices' threshold, matching the anchor for several specific concrete actions.	3 / 3
Completeness	The 'when' is explicit via 'Use when reviewing JavaScript that performs...', but the 'what' (that the skill refactors long tasks to yield via scheduler.yield()) is only implied — the core action is not stated. Not a 3 because the description lacks an explicit statement of what the skill does; not a 1 because the trigger guidance is clearly present.	2 / 3
Trigger Term Quality	Terms like 'reviewing JavaScript', 'synchronous loops', 'tree traversals', and 'bulk DOM updates' give good coverage of natural phrasing a user would use when requesting a JS performance review. Not scored 2 because it goes beyond a single keyword to several relevant variations.	3 / 3
Distinctiveness Conflict Risk	The niche is narrow and specific — JS main-thread long tasks bounded by a 50 ms INP budget — making it unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/scheduler-yield/SKILL.md
Commit: 48405aa

Reviewed: about 8 hours ago

Table of Contents

Discovery Implementation Validation

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.