CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

javascript-pro

Create and debug modern JavaScript code with ES6+, async patterns, and Node.js APIs. Use when working on runtime behavior, promises, or browser and Node compatibility.

Quality

67%

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/agent-ops/javascript-pro/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 body is cleanly sectioned and includes one executable example plus a sensible procedure with a validation feedback loop, but it is undermined by generic template boilerplate, validation guidance that never names a concrete command, a stale Table of Contents missing six of the document's sections, an orphaned 'Redact secrets' bullet with no header, and a broken deep-guidance reference path. It reads as a generic code-review template lightly skinned for JavaScript rather than JS-specific expertise.

Suggestions

Fix the reference path to `references/deep-guidance.md` — the body's `Infrastructure/references/deep-guidance.md` does not exist in the bundle.

Name concrete validation commands in the Validation section (e.g., `node --test`, `npx biome check <files>`) instead of "the relevant local checks".

Repair structure: update the Table of Contents to include the six missing sections (See Also through References and assets), give the orphaned "Redact secrets, tokens, credentials…" bullet a section header, and cut or merge the generic Philosophy/Procedure boilerplate into Core Practices to make room for a second JS-specific code example.

DimensionReasoningScore

Conciseness

Bullets are short and imperative, but several sections add little JS-specific value: a Table of Contents for a ~95-line doc, generic Philosophy boilerplate ("Optimize for clear, verifiable outcomes with the minimum necessary changes"), and rules Claude already knows ("Use `const` by default, `let` only when reassignment is required"). Mostly efficient but could be tightened fits anchor 3; not 2 because there are no concept explanations and every section is brief.

3 / 5

Actionability

One complete executable example exists (the `loadJson` fetch snippet), but the Validation section names no commands ("Run the relevant local checks for touched files and workflow contracts") and error-handling guidance stays abstract ("Surface actionable errors with context"). Some concrete guidance but incomplete with missing key details fits anchor 3; not 4 because the gaps (no validation commands, no error-handling pattern) are more than minor.

3 / 5

Workflow Clarity

The Procedure section gives a clear 3-step sequence with an explicit fail-fast and re-run feedback loop ("Fail fast: stop at the first blocking validation failure", "Re-run checks after fixes"), but checkpoints are never concretized — no command or check is actually named ("Re-run the highest-signal validations"). Sequence present with implicit checkpoints fits anchor 3; not 4 because anchor-4 examples specify actual commands.

3 / 5

Progressive Disclosure

The body is well-sectioned and the deep-guidance reference is clearly signaled with a read-when ("advanced edge cases, migration-safe patterns, or runtime-specific nuance"), but the referenced path `Infrastructure/references/deep-guidance.md` does not exist — the actual file is `references/deep-guidance.md` — so navigation fails as written. Some structure with an undermined reference fits anchor 3; not 4 because a broken path defeats reference navigation, and not 2 because the body is properly sectioned rather than a monolith or inlined bulk content.

3 / 5

Total

12

/

20

Passed

Description

70%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 solid description that explicitly states both what the skill does and when to use it, with natural trigger terms and a mostly distinct JavaScript-runtime niche. Its main limitation is thin action coverage — only 'create and debug' — and a missing synonym/file-extension layer that would sharpen triggering and completeness.

Suggestions

Add one or two more concrete capability verbs to lift specificity, e.g. 'refactor callback code to async/await, fix unhandled promise rejections, and migrate modules between CommonJS and ESM'.

Broaden trigger phrasing to cover user-mention variants and synonyms, e.g. 'Use when the user mentions JavaScript, JS, Node, promises, async/await, or .js files'.

DimensionReasoningScore

Specificity

Names the domain ("ES6+, async patterns, and Node.js APIs") with two concrete actions — "Create and debug modern JavaScript code" — but offers no further specific actions. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'; not 4 because two verbs is not 'several specific actions', and not 2 because the actions stated are concrete rather than generic.

3 / 5

Completeness

Has an explicit what ("Create and debug modern JavaScript code with ES6+, async patterns, and Node.js APIs") and an explicit when ("Use when working on runtime behavior, promises, or browser and Node compatibility"), structurally matching anchor 4's example. Not 5 because the when clause lacks user-mention trigger phrasing (e.g., 'or when the user mentions promises/async'); not 3 because the when is explicit, not missing or weakly implied.

4 / 5

Trigger Term Quality

Includes natural terms users would say — "JavaScript", "promises", "Node.js", "async patterns", "runtime behavior", "browser and Node compatibility" — but misses common variations like "JS", "Node", ".js", or "event loop". Good coverage with a few natural terms missing fits anchor 4; not 5 because it lacks synonyms and file extensions.

4 / 5

Distinctiveness Conflict Risk

The runtime-behavior/async/Node.js framing carves a mostly distinct niche with only minor overlap risk against closely related skills (e.g., TypeScript, linting). Not 5 because "JavaScript code" broadly would also trigger for typed-JS or lint/format tasks where sibling skills apply; not 3 because the ES6+/async/Node-runtime scoping is more specific than anchor-3-level breadth.

4 / 5

Total

15

/

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

jscraik/Agent-Skills

Path

Skills/agent-ops/javascript-pro/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.