CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

modern-javascript-patterns

Master ES6+ features including async/await, destructuring, spread operators, arrow functions, promises, modules, iterators, generators, and functional programming patterns for writing clean, efficient JavaScript code. Use when refactoring legacy code, implementing modern patterns, or optimizing JavaScript applications.

58

Quality

73%

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 ./plugins/javascript-typescript/skills/modern-javascript-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 skill is well-structured for progressive disclosure, with a lean overview pointing cleanly to two real, one-level-deep reference files. However, the body itself offers almost no actionable value for a code skill — it is a generic best-practices list with zero code examples and no concrete workflow.

Suggestions

Add 2-3 short, executable code examples to the body (e.g., a before/after callback-to-async/await refactor) so the top-level content is actionable without opening the references, instead of listing well-known directives like 'Use const by default'.

Replace the 15 generic best-practice bullets with only the non-obvious, opinionated guidance Claude would not already infer, and move the rest into references/details.md.

Cut the introductory paragraph that restates the description, and make the trigger for reading references/details.md concrete (e.g., 'Read details.md when you need worked examples for a specific feature').

DimensionReasoningScore

Conciseness

The body is short and unpadded, but the opening sentence ('Comprehensive guide for mastering modern JavaScript... best practices') duplicates the description, and the 15-bullet best-practices list restates knowledge Claude already has (e.g., 'Use const by default', 'Prefer arrow functions') without adding non-obvious value.

3 / 5

Actionability

There is no executable code anywhere in the body — for a code-patterns skill the guidance is entirely high-level directives ('Use async/await: Instead of Promise chains', 'Avoid mutating data: Use spread operator') with no concrete steps or examples, matching the minimal-guidance anchor rather than the pseudocode anchor.

2 / 5

Workflow Clarity

No multi-step sequence exists (it is a knowledge skill with no risky operations, so no validation cap applies), and the single action — consult references when the overview is insufficient — is stated but loosely defined ('Read that file when the navigation tier above is insufficient'), leaving the sequence implicit.

3 / 5

Progressive Disclosure

The body is a clean overview with both real bundle files (references/details.md, 457 lines; references/advanced-patterns.md, 487 lines) well-signaled, one level deep, and labeled by topic ('Detailed pattern documentation lives in references/details.md'; 'For common pitfalls... see references/advanced-patterns.md'), matching the clear-overview top anchor.

5 / 5

Total

13

/

20

Passed

Description

83%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 strong description that clearly states what the skill covers and when to use it, with an explicit trigger clause and a specific feature list. It is borderline between the top two anchors on completeness and distinctiveness due to one circular trigger phrase and modest overlap with general code-quality skills.

DimensionReasoningScore

Specificity

Enumerates concrete features ('async/await, destructuring, spread operators, arrow functions, promises, modules, iterators, generators') and actions like 'refactoring legacy code', but the lead verb 'Master ES6+ features' is generic, leaving minor gaps versus the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both: the 'what' ('Master ES6+ features... for writing clean, efficient JavaScript code') and a concrete 'when' ('Use when refactoring legacy code, implementing modern patterns, or optimizing JavaScript applications'). The when-clause lists multiple concrete user-facing triggers, matching the top anchor; the circular 'implementing modern patterns' is the only slight weakness.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ('refactoring legacy code', 'optimizing JavaScript applications', 'modern patterns'), but common variations and synonyms like 'modernize', 'ES2015', 'clean up', or a file extension (.js) are missing.

4 / 5

Distinctiveness Conflict Risk

The ES6+/modern-JavaScript niche is mostly distinct, but 'optimizing JavaScript applications' and 'writing clean... code' have minor overlap risk with general refactoring or performance-optimization skills, so it does not reach the minimal-conflict anchor.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

wshobson/agents

Path

plugins/javascript-typescript/skills/modern-javascript-patterns/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.