CtrlK
BlogDocsLog inGet started
Tessl Logo

javascript-pro

Master modern JavaScript with ES6+, async patterns, and Node.js APIs. Handles promises, event loops, and browser/Node compatibility.

49

Quality

53%

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/AI-Agents-Safe-Coding-Skills-claude/skills/javascript-pro/SKILL.md

The canonical home for this skill is javascript-pro in rmyndharis/antigravity-skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 concise and well-structured but the guidance is abstract rather than executable, and the workflow lacks validation checkpoints. It scores well on token efficiency and organization but poorly on actionable specificity.

Suggestions

Replace abstract directives with concrete, copy-paste-ready code snippets or specific commands (e.g., an async/await pattern with try/catch, a Promise.all example, a module export example).

Add explicit validation/verification steps to the workflow where applicable (e.g., "Run the test suite and confirm no unhandled rejections before finishing").

Tighten generic phrases like "Use functional patterns where appropriate" into specific, named recommendations.

DimensionReasoningScore

Conciseness

The body is short, sectioned, and largely assumes Claude's competence; only minor generic phrases like "Use functional patterns where appropriate" and "Handle errors at appropriate boundaries" are trimmable, fitting the efficient-with-minor-over-explanation anchor above the score-3 midpoint.

4 / 5

Actionability

Guidance is high-level hints ("Choose async patterns and module system", "Implement with robust error handling", "Avoid callback hell with modern patterns") with no concrete code, commands, or specific steps to execute; fits the minimal-concrete-guidance anchor and below the pseudocode-level score 3.

2 / 5

Workflow Clarity

Two numbered sequences exist (Instructions 1-4, Approach 1-5) giving a rough sequence, but there are no validation checkpoints or feedback loops; the skill is not destructive/batch so the cap does not apply, placing it at the steps-listed-but-checkpoints-missing anchor.

3 / 5

Progressive Disclosure

The skill is under 50 lines, has no external references needed, and is organized into well-signaled sections (Use this skill when, Do not use, Instructions, Focus Areas, Approach, Output), meeting the simple-skill exception for a top score.

5 / 5

Total

14

/

20

Passed

Description

50%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 clearly identifies the JS/async niche and lists several relevant capability areas, but it lacks an explicit "Use when..." trigger and leans on technical phrasing over natural user language. It sits at the midpoint across all dimensions.

Suggestions

Add an explicit "Use when..." clause naming concrete user triggers (e.g., "Use when debugging async code, the event loop, or migrating legacy JS to ES6+").

Reframe claim language like "Master modern JavaScript with" as concrete actions the skill performs.

Add natural-language synonyms users actually say (e.g., "async", "callback hell", "promises", "Node") and file/extension cues where relevant.

DimensionReasoningScore

Specificity

Names the domain and several concrete capability areas ("ES6+", "async patterns", "Node.js APIs", "promises, event loops", "browser/Node compatibility"), but the "Master modern JavaScript with" framing is claim-like and the actions are capability areas rather than concrete, comprehensive actions; fits the score-3 anchor and falls short of the multi-specific-action coverage of score 4.

3 / 5

Completeness

Provides a clear "what" but no "Use when..." trigger clause, which the guidelines cap at 3; it does not reach the explicit both-what-and-when of score 4 or 5.

3 / 5

Trigger Term Quality

Includes relevant keywords users might say ("modern JavaScript", "async", "promises", "Node.js"), but the phrasing leans technical and omits common natural synonyms and variations a user would naturally voice; closer to score 3 than the comprehensive synonym/extension coverage of score 4.

3 / 5

Distinctiveness Conflict Risk

The async/event-loop focus narrows it, but "modern JavaScript" and "Node.js" are broad enough to overlap with general coding or TypeScript skills, matching the somewhat-specific-but-overlap-risk anchor rather than the mostly-distinct score 4.

3 / 5

Total

12

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.