CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-api-key-value-store-catalog

api/key-value-store — 2 abstractions.

51

Quality

56%

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/key-value-store/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%

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 lean, well-organized catalog that excels at conciseness and structure, but its actionability is limited because it offloads the actual interface and usage to the source file rather than showing a concrete call.

Suggestions

Add a minimal executable example showing how to instantiate and call a store (e.g. set/get a key) so the skill is actionable without reading source.

Optionally include a one-line signature or method summary per abstraction so the interface is visible in the skill body.

DimensionReasoningScore

Conciseness

The body is extremely lean with no padding or explanation of concepts Claude already knows; every line carries import paths or source locations.

3 / 3

Actionability

It gives concrete imports and source paths for locating each abstraction, but delegates the actual interface and usage to the source file, providing no executable calling example.

2 / 3

Workflow Clarity

The 'How to Use' numbered sequence (find abstraction, read source, import, consult pattern skills) is explicit and unambiguous for this simple lookup skill.

3 / 3

Progressive Disclosure

Under 50 lines with clean sections and clearly signaled one-level references to other skills and source files; no nested or monolithic references.

3 / 3

Total

11

/

12

Passed

Description

32%

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 narrowly scoped and distinctive, but it lists no concrete actions, lacks natural trigger terms, and omits any explicit use-when guidance, leaving it incomplete and jargon-heavy.

Suggestions

Add concrete actions the skill enables, e.g. 'Store, retrieve, and scope key-value data via the webiny API key-value store abstractions.'

Include a 'Use when...' trigger clause with natural terms users would say, e.g. 'Use when implementing webiny key-value storage or caching per tenant or globally.'

Replace jargon-only phrasing with plain language so a user needing this skill would naturally match it.

DimensionReasoningScore

Specificity

Names a concrete domain ("api/key-value-store") but states no actual actions beyond a count ("2 abstractions"), so it names the domain without describing capabilities.

2 / 3

Completeness

The "what" is minimal ("2 abstractions") and there is no "Use when..." trigger clause at all, leaving both what and when weak.

1 / 3

Trigger Term Quality

"key-value-store" is technical jargon with no natural phrasing a user would say; no common variations are present.

1 / 3

Distinctiveness Conflict Risk

Scoped to a narrow module ("api/key-value-store") within webiny-api, making it clearly distinct and unlikely to trigger the wrong skill.

3 / 3

Total

7

/

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.