CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-admin-websockets-catalog

admin/websockets — 1 abstractions.

53

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/user-skills/generated/admin/websockets/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 content is a well-organized, concise catalog of one abstraction with a clear usage workflow and a copy-paste import. Its main weakness is deferring the actual interface details to an external source file rather than inlining them.

DimensionReasoningScore

Conciseness

The body is lean with no padding or over-explanation of concepts Claude already knows; the how-to steps and the single abstraction entry each earn their tokens, matching the lean-and-efficient anchor.

5 / 5

Actionability

It provides a concrete copy-paste import line, a source file path, and a clear behavior description, but defers the exact interface and types to "You MUST read the source file", leaving a minor gap that keeps it just below fully executable.

4 / 5

Workflow Clarity

A clear three-step sequence (find abstraction, read source, import) is present and unambiguous, but the mandatory external source-reading step introduces a minor gap with no in-skill checkpoint.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files requiring deeper references, and is organized into clear ## How to Use and ## Abstractions sections, satisfying the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

32%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 is terse and names a specific niche but fails to convey what the skill does or when to use it, with no concrete actions or trigger guidance. It reads more as a catalog header than a skill description.

Suggestions

Add a "Use when..." clause stating when Claude should invoke this skill (e.g., when working with Webiny admin websocket event handlers).

Replace "1 abstractions" with concrete actions, e.g., "Registers handlers that receive every incoming admin websocket message and filter by event action."

Include natural trigger terms like "websocket events", "admin websocket handlers", or "WebsocketEventHandler" that a user would actually say.

DimensionReasoningScore

Specificity

The phrase "admin/websockets — 1 abstractions" names the domain but lists no concrete actions; "1 abstractions" is pure abstract language, fitting between the no-action (1) and minimal-action (2) anchors but closer to naming the domain.

2 / 5

Completeness

It gives only a vague "what" (a catalog of one abstraction) and entirely omits a "when"/Use-when clause, matching the anchor for a vague what with no when.

2 / 5

Trigger Term Quality

"websockets" is a semi-natural keyword but "abstractions" is technical jargon and there are no natural trigger phrases a user would say, matching the anchor for one or two generic keywords missing natural phrasing.

2 / 5

Distinctiveness Conflict Risk

"admin/websockets" is a clear, narrow niche with only minor overlap risk against a general websockets skill, matching the mostly-distinct anchor.

4 / 5

Total

10

/

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