Agent skill · software engineering · nexu-io
od-plugin-authoring
Guided scenario for creating an OpenDesign plugin folder that can be installed into My plugins.
Why this skill is useful
Provides specific guidelines and structure for creating Open Design plugins that the AI wouldn't reliably generate on its own.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 84,236 stars on the source repository.
What this skill does
od-plugin-authoring (scenario) Use this scenario when the user wants to create their own OpenDesign plugin. Required outcome 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. Authoring rules Follow docs/plugins-spec.md and the schema at docs/schemas/open-design.plugin.v1.json. Treat SKILL.md as the canonical behavior description. open-design.json should describe how OpenDesign installs, applies, and presents that behavior. Keep the generated plugin local-user friendly: it should not require marketplace publishing, enterprise trust setup, or private team catalog configuration. Choose a stable plugin id from the user's requested workflow. Use lowercase letters, numbers, dashes, underscores, or dots. Include a short readiness summary when finished: Files created. Whether the folder is ready to add to My plugins. Any validation or follow-up needed before install. A direct next-action prompt that offers: Add to My plugins, Publish repo, or OpenDesign PR. Suggested folder shape The examples/ and assets/ directories are optional. Do not create empty directories just to match the sketch.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nexu-io/od-plugin-authoring