Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →webiny/webiny-admin-tenancy-catalog
admin/tenancy — 9 abstractions.
Passed 21 of 22 test cases with the skill, and 4 of 22 without it.
and 26 more in the full report
17 fixed4 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are defining an admin plugin extension that needs to register a provider dependency against Webiny's admin tenancy context interface. We want to avoid using internal deep package paths like @webiny/app-admin/features/tenancy. Which abstraction symbol should we reference from the main tenancy import?
| Checked | Without skill | With skill |
|---|---|---|
| References TenantContext from webiny/admin/tenancy | Missed | Passed |
| Avoids deep internal source paths in favor of the webiny/admin/tenancy entry point | Missed | Passed |
The instructions your model reads when the skill loads.
import { Name } from "<importPath>";Name: IsNotRootTenant
Import: import { IsNotRootTenant } from "webiny/admin/tenancy"
Source: @webiny/tenant-manager/admin/IsRootTenant.tsx
Name: IsRootTenant
Import: import { IsRootTenant } from "webiny/admin/tenancy"
Source: @webiny/tenant-manager/admin/IsRootTenant.tsx
Name: IsTenant
Import: import { IsTenant } from "webiny/admin/tenancy"
Source: @webiny/tenant-manager/admin/IsRootTenant.tsx
Name: TenantContext
Import: import { TenantContext } from "webiny/admin/tenancy"
Source: @webiny/app-admin/features/tenancy/abstractions.ts
Name: TenantEntry
Kind: type
Import: import type { TenantEntry } from "webiny/admin/tenancy"
Source: @webiny/tenant-manager/admin/types.ts
test cases passed, vs 4 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.