CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

js-redirects

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

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/js-redirects/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.

A well-structured, brief overview that delegates detail to a real one-level-deep reference file, giving excellent progressive disclosure and solid workflow sequencing. The main weakness is that the body itself stays at the directive level — no executable check command or config snippet — leaving the concrete how-to entirely in the referenced file.

Suggestions

Add one concrete detection step to the Check section, e.g. a grep pattern for 'window.location' or a DevTools instruction to filter the Network tab for 3xx responses, so the body is executable without opening the reference.

Include a minimal server-side redirect snippet (nginx/Apache or edge function one-liner) in the Fix section to anchor the 301/302 guidance in executable code.

Fold the 'Explain' section's rationale into the Fix step (one sentence on why server-side is faster/SEO-friendlier) and remove the generic 'Code Review' boilerplate to tighten the token budget.

DimensionReasoningScore

Conciseness

The body is lean — short Quick Reference bullets plus Check/Fix/Explain/Code Review sections — and assumes Claude's competence rather than re-teaching redirect basics. It is not a 5 because the 'Explain' and 'Code Review' sections contain template-like filler ('Explain why server-side redirects are faster... describe the measurement method used to confirm the issue') that could be trimmed.

4 / 5

Actionability

The Fix section gives a concrete direction ('Replace JavaScript-based redirects with server-side 301 or 302 redirects in your web server or edge configuration') and Check names a concrete pattern ('e.g., window.location'), but the body itself contains no executable commands or code — no grep/devtools steps for finding redirects and no server-config examples, which live only in references/rule.md. This lands between the high-level-hints anchor (2) and mostly-executable guidance (4).

3 / 5

Workflow Clarity

Check → Fix → Explain → Code Review forms a clear, ordered sequence for a simple single-purpose skill, and verification is addressed ('describe the measurement method used to confirm the issue', plus dedicated Verification sections in references/rule.md with Lighthouse/PageSpeed/curl checks). It falls short of 5 because the body's own validation checkpoint is only implied via delegation rather than stated as an explicit step.

4 / 5

Progressive Disclosure

The body is a genuine overview (quick reference bullets plus short task sections) with a single, clearly signaled, one-level-deep reference — 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — which exists in the bundle and contains the code examples and verification detail. Content is appropriately split between overview and reference with easy navigation.

5 / 5

Total

16

/

20

Passed

Description

61%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 natural 'Use when' trigger clause with good domain-specific keywords, but it foregrounds the verification workflow while omitting what the skill actually does — replacing JavaScript-based redirects with server-side 301/302 redirects. Adding that remediation statement would lift both completeness and specificity.

Suggestions

State the core action in the description, e.g. 'Replace JavaScript-based redirects (window.location) with server-side 301/302 redirects' — this answers 'what does this do' and raises completeness and specificity.

Add common trigger synonyms such as 'client-side redirects' or 'window.location' so the description matches the phrasing users naturally use when asking about this problem.

Trim the generic verification advice ('Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes') to make room for the skill-specific 'what' without growing the description.

DimensionReasoningScore

Specificity

The description names the domain ('Avoid JavaScript-based redirects', 'slow page loads, heavy assets, or rendering delays') and one or two concrete actions ('Verify the actual bottleneck in DevTools, Lighthouse, or field data'), but never states the skill's core remediation — replacing JS redirects with server-side 301/302 redirects — so coverage is not comprehensive. It sits at the '1-2 concrete actions, not comprehensive' anchor rather than 4, which requires several specific actions, and clearly above 2, since it is more than a bare domain label.

3 / 5

Completeness

The 'when' is explicit ('Use when auditing slow page loads... related to Avoid JavaScript-based redirects'), satisfying the 'Use when...' requirement, but the 'what' is only weakly stated — auditing/verifying is mentioned while the skill's actual remediation is never described. This matches the 'one side clear, the other missing or weakly implied' level better than 4, which requires both what and when to be present and concrete.

3 / 5

Trigger Term Quality

Natural phrases a user would say are present ('slow page loads', 'heavy assets', 'rendering delays', 'JavaScript-based redirects', 'DevTools', 'Lighthouse'), giving good keyword coverage. It falls short of the comprehensive anchor because common variations like 'window.location', 'client-side redirects', 'page speed', or bare 'redirects' are missing.

4 / 5

Distinctiveness Conflict Risk

The JavaScript-redirect niche is narrow and the description is mostly distinct from other skills, though the broad performance triggers ('slow page loads', 'heavy assets', 'rendering delays') create minor overlap risk with sibling performance-audit skills. It is more distinguishable than anchor 3 (generic 'works with X' overlap) but not the minimal-conflict clarity 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/js-redirects/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.