Install any skill in seconds. Free to start, no credit card required.
Get Started Free →webiny/webiny-admin-form-catalog
admin/form — 23 abstractions.
Passed 20 of 22 test cases with the skill, and 4 of 22 without it.
and 25 more in the full report
17 fixed3 passed either way1 still failing1 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.
You are writing a TypeScript helper in a Webiny admin app that receives the imperatively exposed form API object as an argument. Developers typically import `FormAPI` from `@webiny/form`. What is the canonical import path for this type?
| Checked | Without skill | With skill |
|---|---|---|
| Imports type FormAPI from webiny/admin/form. | Missed | Passed |
| Avoids referencing @webiny/form in import statements. | Missed | Passed |
The instructions your model reads when the skill loads.
import { Name } from "<importPath>";Name: Bind
Import: import { Bind } from "webiny/admin/form"
Source: @webiny/form/index.ts
Name: createFieldRenderer
Import: import { createFieldRenderer } from "webiny/admin/form"
Source: @webiny/app-admin/features/formModel/createFieldRenderer.tsx
Name: createObjectFieldRenderer
Import: import { createObjectFieldRenderer } from "webiny/admin/form"
Source: @webiny/app-admin/features/formModel/createFieldRenderer.tsx
Name: FieldBuilder
Import: import { FieldBuilder } from "webiny/admin/form"
Source: @webiny/app-admin/features/formModel/FieldBuilder.ts
Description: Base FieldBuilder with fluent API.
Each method mutates this and returns this for chaining.
Name: FieldType
Import: import { FieldType } from "webiny/admin/form"
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.