Open Design Plugin Authoring
FreeCreate your own Open Design plugins with ease.
Free · Opens the source repo
What Open Design Plugin Authoring does
The Open Design Plugin Authoring skill provides a structured approach for developers who want to create their own plugins for the Open Design platform. This skill guides users through the process of generating a plugin folder that is ready for installation in their workspace. By following the provided instructions, users can ensure that their plugins are compliant with the necessary specifications and include all required files.
When utilizing this skill, the user will produce a folder named generated-plugin/ that contains essential files such as SKILL.md and open-design.json. The SKILL.md file serves as the primary behavior description for the plugin, while the open-design.json file includes critical metadata that defines how the plugin operates within the Open Design ecosystem. This structured approach not only streamlines the plugin creation process but also ensures that the resulting plugins are user-friendly and do not require complex setups like marketplace publishing or enterprise configurations.
This skill is particularly useful for developers and designers looking to extend the functionality of the Open Design platform by creating custom plugins tailored to their specific workflows. By adhering to the authoring rules outlined in the skill, users can produce plugins that are both functional and easy to integrate into their existing projects. The skill also emphasizes the importance of including a readiness summary, which provides users with clear next steps after plugin creation, such as adding to their personal plugin library or publishing the plugin repository.
In summary, the Open Design Plugin Authoring skill offers a comprehensive framework for developing custom plugins, making it an essential tool for anyone looking to enhance their experience with Open Design.
When to use it
Use this skill when you need to create a custom plugin for the Open Design platform to enhance your workflow.
When not to use it
This skill is not suitable for users looking for pre-built plugins or those who do not want to engage in plugin development.
What you can build with it
Creating a Custom Workflow Plugin
A developer wants to create a plugin that automates a specific task within Open Design. Using this skill, they can generate the necessary files and structure for their custom plugin.
Enhancing Design Processes
A designer aims to extend Open Design functionality by developing a plugin tailored to their design processes. This skill provides the guidelines needed to create that plugin.
Testing Plugin Functionality
A user needs to create a plugin for testing purposes. This skill helps them set up the required environment and files quickly.
How to install Open Design Plugin Authoring
View source1. Install with the skills CLI
npx skills add nexu-io/open-design/od-plugin-authoring --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by nexu-iood-plugin-authoring (scenario)
Use this scenario when the user wants to create their own Open Design plugin.
Required outcome
Produce a folder named generated-plugin/ in the active project workspace.
At minimum, the folder must contain:
SKILL.mdwith frontmatter and clear agent instructions.open-design.jsonwith 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.mdand the schema atdocs/schemas/open-design.plugin.v1.json. - Treat
SKILL.mdas the canonical behavior description.open-design.jsonshould describe how Open Design 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 Open Design PR.
Suggested folder shape
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.
Frequently asked questions about Open Design Plugin Authoring
Similar skills
Rhino 3D Scripting
Streamline your Rhinoceros 3D scripting tasks.
MVVM Toolkit
Streamline ViewModel development with source generators.
FreeCAD Scripts
Generate Python scripts for FreeCAD automation and modeling.
Azure Architecture Builder
Design and deploy Azure infrastructure using natural language.
Command Development
Streamline your command creation for Claude Code.
Create Cowork Plugin
Easily build and package plugins through guided sessions.