Name: webiny-api-tenancy-catalog
Rating: 56.8 (1 reviews)
Author: webiny

Blog Docs Log in Get started

webiny-api-tenancy-catalog

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

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

78%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 content is an admirably lean, well-structured abstraction catalog with exact import and source paths and a clear usage workflow. Its main weakness is progressive disclosure: a flat inlined list with no external reference files, and actionability stops short of providing the actual interfaces, deferring them to source.

Suggestions

Move the 17-abstraction catalog into a references file (e.g. references/abstractions.md) and keep SKILL.md as a concise overview that links to it, improving progressive disclosure.

Add a one-line interface/signature hint per abstraction (e.g. key method name and primary parameter) so imports can be used without always opening source.

Group the abstractions by category (e.g. Use Cases, Repositories, Event Handlers, Context) with subheadings to aid navigation within the catalog.

Dimension	Reasoning	Score
Conciseness	The body is a lean four-line-per-abstraction catalog with no padding and no explanation of concepts Claude already knows; every token earns its place, matching the 'lean and efficient' anchor.	5 / 5
Actionability	Each entry gives a copy-paste-ready import path and an exact source file path, but the actual interface/types are deliberately deferred to the source file, leaving a minor gap versus fully executable coverage.	4 / 5
Workflow Clarity	A clear, sequenced four-step 'How to Use' workflow (find, read source, import, see pattern skills) is unambiguous for a lookup skill, though it lacks validation checkpoints that a pure reference skill does not strictly need.	4 / 5
Progressive Disclosure	The skill is a single inlined 17-abstraction catalog over 50 lines with no bundle references or overview-to-detail split; structure exists via 'How to Use' and section separators, but content that could live in a separate reference file is inlined.	3 / 5
	Total	16 / 20 Passed

Description

53%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 a terse module catalog header: it names the tenancy domain and lists abstraction categories, but it provides no concrete actions and no 'Use when' trigger guidance, capping completeness and trigger-term quality. It is reasonably distinct because of its scoped namespace, yet reads more as a label than an activating description.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when implementing tenant lifecycle, installing apps on a tenant, or wiring tenant create/update/delete event handlers.'

Replace abstract category labels with concrete verb-driven actions (e.g. 'Create, update, delete, install, and retrieve tenants; hook into before/after lifecycle events').

Include natural user-facing keywords and synonyms a developer would actually say, such as 'tenant', 'multitenancy', 'install app on tenant', and 'tenant lifecycle hook'.

Dimension	Reasoning	Score
Specificity	It names the tenancy domain and a couple of action categories ('Tenant lifecycle and installation event handlers and use cases'), but these are abstract category labels rather than concrete verb-driven actions, sitting at the 'names domain and 1-2 actions' anchor.	3 / 5
Completeness	It states a weak 'what' (a catalog of 17 abstractions) and entirely lacks a 'Use when...' clause; per the rubric a missing explicit trigger clause caps completeness at 3, and the vague 'what' keeps it from exceeding that cap.	3 / 5
Trigger Term Quality	Relevant domain keywords exist ('Tenant', 'Tenancy', 'lifecycle', 'event handlers') but natural user-facing trigger phrases like 'when creating a tenant' are absent, so it lands at 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The scoped 'API — Tenancy' namespace targets a specific module, making it mostly distinct with only minor overlap risk against sibling tenancy/use-case/event-handler skills.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: webiny/webiny-js
Path: skills/user-skills/generated/api/tenancy/SKILL.md
Commit: d98a4e8

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.