CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-api-tenancy-catalog

API — Tenancy — 17 abstractions. Tenant lifecycle and installation event handlers and use cases.

63

Quality

75%

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/tenancy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 efficient, well-structured catalog that gives executable imports and source paths plus a clear lookup workflow. It earns top marks for token efficiency, actionability, workflow clarity, and organization.

DimensionReasoningScore

Conciseness

The body is a lean catalog: each abstraction carries only Name, Import, Source, and a one-line Description, with no explanation of concepts Claude already knows. Every token earns its place, matching the 'lean and efficient; assumes Claude's competence' anchor.

3 / 3

Actionability

Each entry gives a copy-paste-ready import ('import { Name } from "webiny/api/tenancy"') and an exact source path, and the How-to-Use gives concrete steps, fitting the 'fully executable code/commands; copy-paste ready' anchor.

3 / 3

Workflow Clarity

The four-step How-to-Use sequences find → read source (a MUST checkpoint) → import → consult pattern skills, an unambiguous single-purpose lookup workflow that the simple-skill note allows to score 3; no destructive or batch operation requires additional validation.

3 / 3

Progressive Disclosure

Content is well-organized into How-to-Use and Abstractions sections with one-level-deep pointers (source files and sibling pattern skills) and no nested references; with no bundle files present, the well-organized inline catalog satisfies the simple-skill allowance for a 3.

3 / 3

Total

12

/

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 is a terse auto-generated catalog header that names its domain and abstraction categories but offers no usage triggers and only abstract actions. It is distinguishable enough to avoid gross conflicts yet too vague to guide selection precisely.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with tenant lifecycle, multi-tenancy, or tenant install/uninstall in the webiny API.'

Replace abstract categories with concrete actions a user would name: create, update, delete, install, and retrieve tenants.

Include common variations such as 'multi-tenant', 'tenant onboarding', and 'tenant CRUD' to improve natural trigger matching.

DimensionReasoningScore

Specificity

It names the domain ('Tenancy') and abstraction categories ('tenant lifecycle and installation event handlers and use cases'), but these are codebase categories rather than concrete user-facing actions, matching the 'names domain and some actions, but not comprehensive' anchor. It does not reach 3 because it lists no specific concrete actions like create/delete/install tenant.

2 / 3

Completeness

It weakly answers 'what' (catalogs tenancy abstractions) but provides no 'when' guidance at all — there is no 'Use when...' clause, which per the guidelines caps completeness at 2. It is not a 1 because a domain and purpose are stated.

2 / 3

Trigger Term Quality

Terms like 'Tenancy', 'Tenant', 'lifecycle', and 'installation' are relevant, but the phrasing leans on technical jargon ('event handlers', 'use cases') and omits common variations a user might say (e.g. 'create tenant', 'delete tenant', 'multi-tenant'), fitting the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

'Tenancy' is a reasonably specific niche, but as one of several sibling webiny-api catalog skills it could overlap with adjacent catalogs, matching 'somewhat specific but could still overlap with similar skills.' It lacks the distinct explicit triggers needed for a 3.

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.