CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-use-case-pattern

UseCase implementation pattern — DI, Result handling, error types, decorators, CMS repositories, entry mappers, and schema-based permissions. Use this skill to implement, inject, override, or decorate any Webiny UseCase, or to build repositories that persist data via CMS.

74

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, highly actionable body of Webiny-specific patterns with concrete code and explicit verification checkpoints. The main gap is progressive disclosure: it is a long single-file document that could offload some detailed patterns into reference files.

DimensionReasoningScore

Conciseness

The body is dense Webiny-specific knowledge Claude does not already know (Result pattern quirks, the "never use result.isError()" gotcha, mandatory .js import paths) with no padding explaining basics, so every token earns its place.

3 / 3

Actionability

It provides fully executable TypeScript templates, concrete import paths, real error class definitions, and a specific deploy command ("yarn webiny deploy api --env=dev"), making the guidance copy-paste ready.

3 / 3

Workflow Clarity

The "Resolving Types (MANDATORY)" section is an explicit pre-coding verification checkpoint, the registration section uses "YOU MUST" rules, and the "Key Rules" section acts as a checklist, giving clear sequencing with validation steps.

3 / 3

Progressive Disclosure

Sections are well organized and it appropriately delegates permissions to a sibling skill, but the ~450-line body is a monolith with no bundle/reference files, and the detailed code-heavy patterns (abstractions, CMS repository, decorators) could plausibly be split into reference files.

2 / 3

Total

11

/

12

Passed

Description

92%

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 specific, action-oriented description with an explicit "Use when" trigger and good domain-term coverage. Its only weakness is overlap with sibling skills via the DI and permissions topics listed in the trigger.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "implement, inject, override, or decorate any Webiny UseCase, or to build repositories that persist data via CMS" — rather than vague language, matching the anchor for listing several specific actions.

3 / 3

Completeness

It answers both "what" ("UseCase implementation pattern — DI, Result handling, error types, decorators, CMS repositories, entry mappers, and schema-based permissions") and "when" via the explicit "Use this skill to..." trigger clause.

3 / 3

Trigger Term Quality

It covers natural terms a Webiny developer would actually say ("implement/decorate/override a UseCase", "CMS repositories", "persist data via CMS"), giving good domain-term coverage rather than only jargon.

3 / 3

Distinctiveness Conflict Risk

The core UseCase/repository niche is distinct, but the description enumerates "DI" and "schema-based permissions" which overlap with dedicated sibling skills (webiny-dependency-injection, webiny-api-permissions), so it could trigger for the wrong skill.

2 / 3

Total

11

/

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.