CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-api-system-catalog

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

58

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

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

85%

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

A tidy, well-structured catalog that is token-efficient and clearly sequenced. Its main gap is actionability: it hands over imports and source paths but pushes the actual interface to the source file rather than inlining it.

Suggestions

Inline a minimal signature or usage snippet for each abstraction (constructor params / handler shape) so the skill is actionable without opening the source file.

Optionally add a one-line example invocation per abstraction to demonstrate correct usage beyond the bare import.

DimensionReasoningScore

Conciseness

The body is lean and efficient — a short usage sequence plus compact per-abstraction entries with no padding and no explanation of concepts Claude already knows.

3 / 3

Actionability

Concrete, copy-paste-ready import statements and source paths are given, but it explicitly defers the exact interface/types to the source file ('You MUST read the source file'), leaving key usage details incomplete.

2 / 3

Workflow Clarity

The 'How to Use' list is a clear 4-step sequence (find → read source → import → consult pattern skills) for a low-risk catalog lookup, so no validation checkpoint is needed.

3 / 3

Progressive Disclosure

Under 50 lines with no bundle files; it is well-organized into 'How to Use' and 'Abstractions' sections and points one level deep to sibling pattern skills, matching the simple-skill allowance.

3 / 3

Total

11

/

12

Passed

Description

50%

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 tersely names its domain and a couple of actions but lacks any explicit use-when trigger and leans on technical jargon. It is serviceable but not standout — missing the 'when' half of the what/when pair.

Suggestions

Add an explicit 'Use when ...' clause naming the situations that should trigger this skill (e.g., 'Use when implementing system-wide installation logic or hooking into the post-install lifecycle').

Replace jargon ('abstractions', 'use cases') with more natural trigger terms a user would actually say, such as 'install the system' or 'run after system install'.

Make the distinctiveness sharper than 'System' by leading with 'System installation' so it cannot be confused with other webiny-api catalog skills.

DimensionReasoningScore

Specificity

Names the domain ('System installation') and some actions ('event handlers and use cases') but stops short of listing multiple concrete, comprehensive actions.

2 / 3

Completeness

It states what the skill covers ('System installation event handlers and use cases') but provides no 'Use when...' clause or explicit trigger guidance, capping completeness at 2.

2 / 3

Trigger Term Quality

'System installation' and 'event handlers' are relevant keywords a developer might say, but it leans on jargon ('abstractions', 'use cases') and misses common variations like 'install' or 'setup'.

2 / 3

Distinctiveness Conflict Risk

Within the webiny-api context the 'System installation' niche is somewhat specific, but the bare 'System' label is generic and could overlap with sibling catalog skills.

2 / 3

Total

8

/

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.