CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-admin-tenancy-catalog

admin/tenancy — 9 abstractions.

49

Quality

53%

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/admin/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 a tight, well-structured catalog: concrete import statements and source paths for each of the nine abstractions, a clear 3-step usage workflow, and clean sectioning with no wasted tokens.

DimensionReasoningScore

Conciseness

The body is lean: a 3-line How-to-Use and per-entry Name/Import/Source lines with no padding and no explanation of concepts Claude already knows, matching 'lean and efficient; every token earns its place'.

3 / 3

Actionability

Each entry gives a copy-paste-ready import statement (e.g. `import { IsRootTenant } from "webiny/admin/tenancy"`) plus a concrete source path, and the instruction to read the source for exact interfaces is directly actionable, fitting 'fully executable; copy-paste ready'.

3 / 3

Workflow Clarity

The simple lookup workflow is clearly sequenced (find the abstraction -> read its source file -> import it) and unambiguous; as a low-risk single-purpose catalog it needs no validation checkpoint, so the simple-skill allowance applies.

3 / 3

Progressive Disclosure

With no bundle files present, the under-50-line body is cleanly organized into How to Use and Abstractions sections with consistent per-entry blocks and clearly signaled one-level source references, satisfying the simple-skill well-organized-sections criterion.

3 / 3

Total

12

/

12

Passed

Description

7%

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 label rather than a capability statement: it identifies the domain and abstraction count but conveys no actions, no natural trigger terms, and no explicit 'when to use' guidance.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when you need to import admin/tenancy abstractions such as IsRootTenant, TenantContext, useCurrentTenant, or useTenantContext for the webiny-api codebase.'

Replace the bare label with concrete actions, e.g. 'Catalogs the 9 admin/tenancy React abstractions available from webiny/admin/tenancy, giving each one's import statement and source file location.'

Include natural trigger terms a user would actually say, such as 'tenant', 'current tenant hook', 'root-tenant check', or 'webiny tenancy', instead of only the module-path jargon.

DimensionReasoningScore

Specificity

The phrase "admin/tenancy — 9 abstractions." names a domain and a count but describes zero concrete actions; it labels rather than instructs, matching the 'vague or no actions' anchor.

1 / 3

Completeness

It weakly gestures at 'what' (9 abstractions) without saying what the skill does with them, and the 'when' trigger is entirely absent, so both halves are weak/missing per the lowest anchor.

1 / 3

Trigger Term Quality

Only terms present are the internal jargon "admin/tenancy" and "abstractions" with no natural user-facing keywords and no 'Use when' phrasing, fitting the 'no natural keywords; technical jargon' anchor.

1 / 3

Distinctiveness Conflict Risk

The named niche "admin/tenancy" is somewhat specific to the webiny-api context, but the bare description provides no distinct triggers and could overlap with other webiny admin/tenancy skills, matching 'somewhat specific but could still overlap'.

2 / 3

Total

5

/

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.