Source profileQuality 75/100

nexu-io/open-design/plugins/_official/scenarios/od-plugin-authoring/SKILL.md

od-plugin-authoring

Guided scenario for creating an Open Design plugin folder that can be installed into My plugins.

Source repository stars
82,073
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

Use this scenario when the user wants to create their own Open Design 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

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability 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/89d6d4ef21baf80f871595abdf6f7de6e941dd44/plugins/_official/scenarios/od-plugin-authoring/SKILL.md at commit 89d6d4ef21baf80f871595abdf6f7de6e941dd44. 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

    1. 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:
    2. 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 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.
    3. 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
    SignalValueEvidence typeMeaning
    Quality score75/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars82,073SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated 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
    89d6d4ef21baf80f871595abdf6f7de6e941dd44
    License
    Apache-2.0
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    od-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.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 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.

    Alternatives

    Compare before choosing

    Computed 10042,015

    coreyhaines31/marketingskills

    ab-testing

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

    2026-07-270 platforms
    Computed 10042,015

    coreyhaines31/marketingskills

    churn-prevention

    When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

    2026-07-270 platforms
    Computed 1007

    event4u-app/agent-config

    design-intelligence

    Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

    2026-07-280 platforms
    Computed 1007

    event4u-app/agent-config

    design-system-capture

    Write and maintain DESIGN.md + PRODUCT.md — captures visual decisions and interaction patterns so design tasks stay consistent across sessions without re-scanning past work.

    2026-07-280 platforms