CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-api-db-catalog

api/db — 3 abstractions.

44

Quality

46%

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/db/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 body is a concise, well-structured catalog that gets Claude to the right import and source file quickly, with a clear lookup workflow and appropriately one-level-deep references. Its only real gap is actionability: it hands off the interface and concrete usage to the source file rather than showing a minimal usage example inline.

Suggestions

Add a one-line minimal usage example for at least one abstraction (e.g. a FilterUtil call) so Claude has executable guidance without opening the source file.

Briefly note what each abstraction is for (e.g. "ValueFilterRegistry — register custom filter operators") so the catalog guides selection without requiring a source read first.

DimensionReasoningScore

Conciseness

The body is a lean catalog of Name/Import/Source entries plus a brief 4-step How-to-Use; it explains no concepts Claude already knows and every label earns its place, matching the score-3 lean-and-efficient anchor.

3 / 3

Actionability

It supplies copy-paste import statements and exact source paths, but defers the actual interface and usage to the source file ("You MUST read the source file to get the exact interface and types"), leaving key usage details missing per the score-2 anchor.

2 / 3

Workflow Clarity

This is a simple, under-50-line lookup skill with a clear 4-step sequence (find → read source → import → see patterns); it involves no destructive or batch operations, so the simple-skills note permits a 3 without validation checkpoints.

3 / 3

Progressive Disclosure

Under 50 lines with no bundle files, the skill is well organized into How-to-Use and Abstractions sections; its inline references to source files and sibling skills are one level deep and clearly signaled, satisfying the under-50-lines guideline for a 3.

3 / 3

Total

11

/

12

Passed

Description

7%

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 an unhelpfully terse label: it names a module and a count of abstractions but describes no capabilities and gives no usage triggers, so it would rarely be surfaced when needed. It is only saved from the lowest band by the somewhat-specific "api/db" niche marker.

Suggestions

Add concrete actions, e.g. "Catalogs the FilterUtil, ValueFilter, and ValueFilterRegistry abstractions in the api/db package and shows how to import them."

Append an explicit trigger clause such as "Use when working with Webiny api/db filtering abstractions or when the user asks how to filter/query data via api/db."

Replace the jargon "3 abstractions" with the natural terms a user would say (e.g. "filtering", "query filters", "data filtering").

DimensionReasoningScore

Specificity

The phrase "api/db — 3 abstractions." names a module but states only a count of abstractions; it lists no concrete actions, making it vaguer than the score-2 anchor "Processes PDF files and extracts content".

1 / 3

Completeness

It barely answers "what" ("3 abstractions" with no behavior) and has no "when to use it" trigger at all, so both halves are weak per the score-1 anchor.

1 / 3

Trigger Term Quality

"api/db" and "abstractions" are technical jargon a user would not naturally say when they need this skill, matching the score-1 anchor of technical jargon with no natural keywords.

1 / 3

Distinctiveness Conflict Risk

"api/db" identifies a specific module niche, distinguishing it somewhat from sibling skills, but the generic "3 abstractions" and absence of distinct triggers leave overlap risk, matching the score-2 anchor.

2 / 3

Total

5

/

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.