CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-api-system-catalog

API — System — 2 abstractions. System installation event handlers and use cases.

58

Quality

66%

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/system/SKILL.md
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 a tight, well-structured catalog that earns its tokens and navigates cleanly to sibling skills and source files. Its only real gap is the absence of concrete usage code, which would lift actionability from good to fully executable.

Suggestions

Add a one-line runnable example per abstraction (e.g. instantiating InstallSystemUseCase or registering SystemInstalledEventHandler) so guidance is fully copy-paste executable.

Optionally link the source paths as clickable references and confirm the sibling skill names resolve, to make navigation even more explicit.

DimensionReasoningScore

Conciseness

The body is lean and efficient: short 'How to Use' steps and per-abstraction stubs with only Name/Import/Source/Description, assuming Claude's competence with no concept re-explanation.

5 / 5

Actionability

Provides copy-paste-ready import statements and exact source paths, but stops short of executable usage examples, deferring those to the source file and sibling pattern skills.

4 / 5

Workflow Clarity

The 'How to Use' section gives a clear 4-step lookup sequence with an explicit 'MUST read the source file' checkpoint; no validation feedback loop is needed since this is a non-destructive catalog lookup.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files present; content is cleanly split into 'How to Use' and 'Abstractions' sections, and references to sibling skills and source files are one level deep and clearly signaled.

5 / 5

Total

18

/

20

Passed

Description

46%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 concise and names its niche, but it is jargon-heavy and lacks any explicit 'when to use' trigger guidance, which caps its completeness and trigger-term quality. Adding a 'Use when...' clause with natural phrasing would meaningfully raise the score.

Suggestions

Add an explicit trigger clause, e.g. 'Use when implementing or hooking into webiny system installation, or when the user mentions installing the system / system lifecycle events.'

Replace generic nouns ('abstractions', 'use cases') with more natural user-facing terms and synonyms (e.g. 'install the system', 'run system setup', 'react to system-installed events').

Keep the catalog count ('2 abstractions') but pair it with concrete verbs describing what each does, to lift specificity beyond category labels.

DimensionReasoningScore

Specificity

Names the domain ('System installation') and two concrete abstraction types ('event handlers and use cases'), but these are category nouns rather than a comprehensive list of actions.

3 / 5

Completeness

Clearly states what the skill covers ('System installation event handlers and use cases') but has no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Relies on technical jargon ('abstractions', 'event handlers', 'use cases') with only one mildly natural phrase ('System installation'); missing the common variations a user would actually say.

2 / 5

Distinctiveness Conflict Risk

Targets a clear niche (webiny api-system installation lifecycle) that is mostly distinct, with only minor overlap risk against other webiny pattern skills.

4 / 5

Total

12

/

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.