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.

71

Quality

86%

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

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 body is an actionable, well-structured pattern reference with executable examples and mandatory verification steps. Trimming the import-listing block and adding an explicit error-recovery loop would push conciseness and workflow clarity to full marks.

Suggestions

Condense the 'Common CMS Use Cases for Repositories' import block into a compact table or a single grouped import statement to improve conciseness.

Add a short numbered feedback loop for repository/use-case failure (e.g., on isFail -> inspect error.code -> wrap in domain error -> re-emit) to strengthen workflow clarity.

De-duplicate the repeated 'Export as default' rule across sections into one consolidated 'Registration & Export' rule block.

DimensionReasoningScore

Conciseness

Dense, code-heavy, and largely assumes Claude's competence; mostly lean with every section earning its place. Sits at 4 rather than 5 because the long CMS-import listing block and some repeated 'Rules' bullets could be trimmed.

4 / 5

Actionability

Provides multiple complete, copy-paste-ready TypeScript examples (UseCase, repository, decorator, mapper, errors, abstractions, registration) covering the common cases, each paired with explicit rules.

5 / 5

Workflow Clarity

Sequenced guidance (resolve model first, check isFail, wrap errors, singleton scope) plus a mandatory 'Resolving Types' verification checkpoint; not a 5 because there is no explicit error-recovery feedback loop in numbered-workflow form.

4 / 5

Progressive Disclosure

Single, well-organized SKILL.md with clearly labeled sections and pointers to related skills; no in-repo reference files are needed, so the simple-skill allowance for clean structure yields a 5.

5 / 5

Total

18

/

20

Passed

Description

87%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 strong: it states concrete capabilities, provides an explicit 'Use this skill to...' trigger clause, and occupies a distinct niche. Minor gains are possible by adding more colloquial trigger synonyms.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete capabilities (DI, Result handling, error types, decorators, CMS repositories, entry mappers, schema-based permissions), matching the score-4 anchor; not a 5 because the actions are abstract categories rather than a maximally concrete enumerated list.

4 / 5

Completeness

Explicitly answers both 'what' (the UseCase implementation pattern and its components) and 'when' ('Use this skill to implement, inject, override, or decorate any Webiny UseCase, or to build repositories that persist data via CMS') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes several natural developer trigger phrases ('implement, inject, override, or decorate any Webiny UseCase', 'build repositories that persist data via CMS') with synonyms; missing a few common variations, so it sits at 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Targets a clear, framework-specific niche (Webiny UseCase, CMS repositories, schema-based permissions) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

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.

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