CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-api-tenant-manager-catalog

API — Tenant Manager — 9 abstractions. Tenant management event handlers and use cases.

65

Quality

78%

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/tenant-manager/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 a well-structured, token-efficient catalog that gives executable imports, exact source paths, and a clear usage sequence while deferring deeper detail to source and pattern skills. It exemplifies appropriate progressive disclosure for a catalog skill.

DimensionReasoningScore

Conciseness

The body is a lean, structured catalog with no concept over-explanation and assumes Claude's competence (defers interface details to source); every token earns its place, matching the 'lean and efficient' anchor.

3 / 3

Actionability

Each abstraction ships a concrete, copy-paste-ready import statement and an exact source path, and the 'How to Use' steps give a generic import pattern; this matches the 'fully executable, copy-paste ready' anchor rather than the vague or pseudocode anchors.

3 / 3

Workflow Clarity

A clear 4-step 'How to Use' sequence with an explicit checkpoint (step 2: 'You MUST read the source file') before importing; no destructive/batch operations exist that would require a validate-fix-retry loop, so the cap does not apply.

3 / 3

Progressive Disclosure

Content is split into well-organized sections ('How to Use', 'Abstractions') with one-level references to source files and to the use-case/event-handler pattern skills; no nested references, matching the 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

12

/

12

Passed

Description

57%

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 identifies a clear niche and the right domain vocabulary but stops at naming categories rather than concrete actions and omits any 'use when' trigger guidance. It is serviceable yet under-specified for discovery.

Suggestions

Add a 'Use when...' clause stating when to reach for this skill (e.g., when implementing or wiring up tenant lifecycle operations in the webiny-api).

Replace the generic 'event handlers and use cases' phrasing with a few concrete verbs the abstractions perform (create, disable, enable, update, retrieve tenants).

Include a couple of natural user-facing trigger terms (e.g., 'tenant lifecycle', 'multi-tenant setup', 'tenant CRUD') alongside the internal jargon.

DimensionReasoningScore

Specificity

Names the domain ("Tenant management") and capability categories ("event handlers and use cases") but lists no concrete actions like create/disable/enable, matching the 'names domain and some actions, but not comprehensive' anchor; not a 3 because no specific concrete actions are enumerated.

2 / 3

Completeness

Answers 'what' ("9 abstractions", "event handlers and use cases") but provides no 'when' guidance — there is no 'Use when...' clause, which per the guidelines caps completeness at 2; not a 3 because the trigger/when element is entirely missing.

2 / 3

Trigger Term Quality

Contains relevant domain keywords ("Tenant Manager", "tenant management") a user might say, but they are codebase-internal jargon without natural variations; not a 1 because the terms are domain-relevant, not a 3 because coverage is thin and technical.

2 / 3

Distinctiveness Conflict Risk

Tied to a specific named module ("API — Tenant Manager") with a clear niche, making it unlikely to trigger for the wrong skill; not a 2 because the scope is narrow and unambiguous.

3 / 3

Total

9

/

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.