Install any skill in seconds. Free to start, no credit card required.
Get Started Free →webiny/webiny-admin-lexical-catalog
admin/lexical — 17 abstractions.
Passed 23 of 23 test cases with the skill, and 3 of 23 without it.
and 14 more in the full report
20 fixed3 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 20 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am writing a full toolbar extension file for Webiny Lexical editor. What is the unified import path for DropDown, useRichTextEditor, and useTypographyAction?
| Checked | Without skill | With skill |
|---|---|---|
| Imports all required UI components and hooks from a single package path. | Passed | Passed |
| Uses the import path webiny/admin/lexical. | Missed | Passed |
| Imports the useTypographyAction hook. | Passed | Passed |
The instructions your model reads when the skill loads.
import { Name } from "<importPath>";Name: Divider
Import: import { Divider } from "webiny/admin/lexical"
Source: @webiny/lexical-editor/ui/Divider.tsx
Name: DropDown
Import: import { DropDown } from "webiny/admin/lexical"
Source: @webiny/lexical-editor/ui/DropDown.tsx
Name: DropDownItem
Import: import { DropDownItem } from "webiny/admin/lexical"
Source: @webiny/lexical-editor/ui/DropDown.tsx
Name: getNodeFromSelection
Import: import { getNodeFromSelection } from "webiny/admin/lexical"
Source: @webiny/lexical-editor/hooks/index.ts
Name: Klass
Kind: type
Import: import type { Klass } from "webiny/admin/lexical"
Source: @webiny/lexical-editor/types.ts
test cases passed, vs 3 / 23 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.