CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-api-opensearch-catalog

api/opensearch — 4 abstractions.

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

Quality

Content

85%

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 clean, concise abstraction catalog with a clear usage sequence and well-organized references. Its only gap is the absence of any executable usage example, leaving the user to read source files for actual interfaces.

DimensionReasoningScore

Conciseness

The body is lean — just names, import paths, source paths, and a 4-step how-to — with no concept explanations Claude already knows and every token earning its place.

3 / 3

Actionability

Import statements and source paths are concrete and copy-paste ready, but no executable usage example is given; the body defers entirely to reading the source files.

2 / 3

Workflow Clarity

This is a simple, under-50-line single-purpose catalog with an unambiguous 4-step sequence and no destructive or batch operations requiring validation checkpoints.

3 / 3

Progressive Disclosure

Sections are well organized with one-level-deep pointers to source files and related pattern skills, no nested references, and no bundle files are needed for this short overview.

3 / 3

Total

11

/

12

Passed

Description

22%

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 extremely terse, naming only the domain and an abstraction count with no concrete actions or usage triggers. It fails to tell Claude what the skill does or when to reach for it.

Suggestions

Add concrete actions the skill supports, e.g. "create OpenSearch clients, manage search contexts, and factories".

Add an explicit trigger clause such as "Use when working with OpenSearch indexing, search queries, or the webiny api/opensearch package".

Drop the jargon term "abstractions" in favor of user-natural language like "client, context, and factory utilities".

DimensionReasoningScore

Specificity

The description "api/opensearch — 4 abstractions." names the domain but lists no concrete actions; "4 abstractions" is a count, not an action like extracting or querying.

1 / 3

Completeness

It answers neither "what does this do" nor "when should Claude use it", and there is no "Use when…" clause (which would cap completeness at 2 regardless).

1 / 3

Trigger Term Quality

"opensearch" is a natural keyword a user would say, but it is surrounded by jargon ("abstractions", "api/") and common variations (search, index, query) are missing.

2 / 3

Distinctiveness Conflict Risk

OpenSearch is a specific niche, but the description is so minimal and trigger-free that it could overlap with other opensearch-related skills.

2 / 3

Total

6

/

12

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
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.