Source profileQuality 67/100

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

od-default

Hidden fallback scenario for free-form Home prompts. Ask the task type first, then continue through the matching Open Design flow.

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

Decision brief

What it does—and where it fits

This plugin runs only when the user types a free-form Home prompt without choosing one of the visible category chips. It is the design-engine fallback, not a visible catalog entry.

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-default"
    Safe inspection promptEditorial

    Inspect the Agent Skill "od-default" from https://github.com/nexu-io/open-design/blob/89d6d4ef21baf80f871595abdf6f7de6e941dd44/plugins/_official/scenarios/od-default/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

      Turn 1: ask the task type and lock the brief

      Your first response must be one short sentence plus this structured form, then stop. Do not write files, use tools, or start planning until the user answers. Localize every user-facing string to the user's chat language, but keep ids, types, option values, and the ordered taskTy…

      Your first response must be one short sentence plus this structured form, then stop. Do not write files, use tools, or start planning until the user answers. Localize every user-facing string to the user's chat language…
    2. 02

      After the answer

      When the user replies with [form answers — task-type], bind the chosen task type as authoritative and continue:

      Prototype: run the normal new-generation prototype flow.Live artifact: create a live HTML/CSS/JS artifact and register it forSlide deck: follow the deck workflow and framework rules.

    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 score67/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-default/SKILL.md
    Commit
    89d6d4ef21baf80f871595abdf6f7de6e941dd44
    License
    Apache-2.0
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    od-default (hidden scenario)

    This plugin runs only when the user types a free-form Home prompt without choosing one of the visible category chips. It is the design-engine fallback, not a visible catalog entry.

    Turn 1: ask the task type and lock the brief

    Your first response must be one short sentence plus this structured form, then stop. Do not write files, use tools, or start planning until the user answers. Localize every user-facing string to the user's chat language, but keep ids, types, option values, and the ordered taskType options stable. Prefill each question's default from the brief, including the taskType option you recommend, so the user can submit the form unchanged.

    <question-form id="task-type" title="Choose the task type">
    {
      "lang": "en",
      "description": "I'll route this through the right Open Design workflow and lock the brief in one shot. Prefilled for you — send as is, or adjust first.",
      "questions": [
        {
          "id": "taskType",
          "label": "What should I build?",
          "type": "radio",
          "required": true,
          "allowCustom": false,
          "options": [
            "Prototype",
            "Live artifact",
            "Slide deck",
            "Image",
            "Video",
            "HyperFrames",
            "Audio",
            "Other"
          ]
        },
        {
          "id": "audience",
          "label": "Who is this for?",
          "type": "text",
          "placeholder": "Target user, buyer, viewer, or audience..."
        },
        {
          "id": "brand",
          "label": "Brand context",
          "type": "radio",
          "options": [
            { "label": "Pick a direction for me", "value": "pick_direction" },
            { "label": "I have a brand spec — I'll share it", "value": "brand_spec" },
            { "label": "Match a reference site / screenshot — I'll attach it", "value": "reference_match" }
          ]
        },
        {
          "id": "scale",
          "label": "Roughly how much?",
          "type": "text",
          "placeholder": "e.g. 8 slides, 1 landing + 3 sub-pages, 4 mobile screens, 30s video"
        },
        {
          "id": "speakerNotes",
          "label": "For slide decks, include speaker notes?",
          "type": "switch",
          "defaultValue": true
        },
        {
          "id": "constraints",
          "label": "Any important constraints?",
          "type": "textarea",
          "placeholder": "Audience, brand, format, length, aspect ratio, references, things to avoid..."
        }
      ]
    }
    </question-form>
    

    After the answer

    When the user replies with [form answers — task-type], bind the chosen task type as authoritative and continue:

    • Prototype: run the normal new-generation prototype flow.
    • Live artifact: create a live HTML/CSS/JS artifact and register it for preview when tooling is available.
    • Slide deck: follow the deck workflow and framework rules.
    • Image: plan a concrete image prompt, then use the OD media generation CLI for image output.
    • Video: plan shots, duration, aspect, and motion, then use the OD media generation CLI for video output.
    • HyperFrames: create HTML-driven motion frames or a HyperFrames-ready motion artifact before rendering/exporting.
    • Audio: plan voice/music/SFX intent, then use the OD media generation CLI for audio output.
    • Other: ask only the minimum follow-up needed, then choose the closest Open Design workflow and continue.

    This single form already locks the discovery brief. Do not emit a second <question-form id="discovery">; proceed directly to the matching planning, generation, and critique stages. Do not tell the user to go back and choose a chip; the default plugin owns this fallback.

    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

    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

    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.

    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.