Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nexu-io/od-plugin-authoring
Guided scenario for creating an Open Design plugin folder that can be installed into My plugins.
Passed 17 of 23 test cases with the skill, and 10 of 23 without it.
and 12 more in the full report
9 fixed8 passed either way4 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
Which JSON schema file in docs/schemas/ should be followed when constructing the OpenDesign plugin configuration?
| Checked | Without skill | With skill |
|---|---|---|
| References the schema path docs/schemas/open-design.plugin.v1.json. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this scenario when the user wants to create their own OpenDesign plugin.
Produce a folder named generated-plugin/ in the active project workspace.
At minimum, the folder must contain:
SKILL.md with frontmatter and clear agent instructions.open-design.json with valid plugin metadata, od.kind, mode, task kind, capabilities, and inputs when needed.Add examples/, assets/, or other supporting files only when they help the plugin be used or reviewed.
docs/plugins-spec.md and the schema at docs/schemas/open-design.plugin.v1.json.SKILL.md as the canonical behavior description. open-design.json should describe how OpenDesign installs, applies, and presents that behavior.generated-plugin/
SKILL.md
open-design.json
examples/
assets/
The examples/ and assets/ directories are optional. Do not create empty directories just to match the sketch.
test cases passed, vs 10 / 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.