od-plugin-authoring by nexu-io

Decision brief

What it does: where it fits

Use this scenario when the user wants to create their own OpenDesign plugin.

Best for

Not for

Tasks that require unconfirmed production actions or broad system permissions.
Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

Platform	Status	Evidence	What to check
Codex	Not declared	No explicit evidence	Portability before use
Claude Code	Not declared	No explicit evidence	Portability before use
Cursor	Not declared	No explicit evidence	Portability before use
Gemini CLI	Not declared	No explicit evidence	Portability before use

Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource

npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/scenarios/od-plugin-authoring"

Safe inspection promptEditorial

Inspect the Agent Skill "od-plugin-authoring" from https://github.com/nexu-io/open-design/blob/edfa6b5f447e95cb120eae030f03baba00dc34de/plugins/_official/scenarios/od-plugin-authoring/SKILL.md at commit edfa6b5f447e95cb120eae030f03baba00dc34de. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

01
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.Produce a folder named generated-plugin/ in the active project workspace. At minimum, the folder must contain:
02
Authoring rules
Follow docs/plugins-spec.md and the schema at docs/schemas/open-design.plugin.v1.json.
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.
03
Suggested folder shape
The examples/ and assets/ directories are optional. Do not create empty directories just to match the sketch.
The examples/ and assets/ directories are optional. Do not create empty directories just to match the sketch.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial

Signal	Value	Evidence type	Meaning
Quality score	73/100	Computed	Documentation, specificity, maintenance, and trust rules
Repository stars	91,167	Source	Repository attention, not individual Skill quality
Compatibility	0 platforms	Source	Declared in the catalog source record
Usage guide	automated source guide	Editorial	Generated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository: nexu-io/open-design
Skill path: plugins/_official/scenarios/od-plugin-authoring/SKILL.md
Commit: edfa6b5f447e95cb120eae030f03baba00dc34de
License: Apache-2.0
Collected: 2026-08-25
Default branch: main

View the original SKILL.md

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

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

What to verify before installation and use

What does the od-plugin-authoring source document cover?

Use this scenario when the user wants to create their own OpenDesign plugin.

How do I install od-plugin-authoring?

The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/scenarios/od-plugin-authoring". Inspect the command and pinned source before running it.