Source profileQuality 66/100Review permissions

nexu-io/open-design/plugins/_official/examples/od-plugin-contribute-open-design/SKILL.md

od-plugin-contribute-open-design

Open a pull request adding a local OpenDesign plugin to the OpenDesign community catalog using gh CLI.

Source repository stars
91,167
Declared platforms
0
Static risk flags
2
Last source update
2026-08-25
Source checked
2026-08-25

Decision brief

What it does: where it fits

Use this workflow when the active project contains a copied plugin folder and the user wants to propose it for the OpenDesign community catalog.

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/examples/od-plugin-contribute-open-design"
    Safe inspection promptEditorial

    Inspect the Agent Skill "od-plugin-contribute-open-design" from https://github.com/nexu-io/open-design/blob/edfa6b5f447e95cb120eae030f03baba00dc34de/plugins/_official/examples/od-plugin-contribute-open-design/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

    1. 01

      Workflow

      1. Read the active plugin inputs. plugincontextpath is the copied plugin folder relative to the project working directory. 2. Inspect the copied plugin's manifest, skill instructions, examples, and compatibility metadata. 3. Call the local daemon endpoint instead of hand-rolling…

      Read the active plugin inputs. plugincontextpath is the copied plugin folder relative to the project working directory.Inspect the copied plugin's manifest, skill instructions, examples, and compatibility metadata.Call the local daemon endpoint instead of hand-rolling GitHub commands:

    Permission review

    Static risk signals and limitations

    Sends data out

    high · line 11

    The documentation includes sending, uploading, or posting data to a remote service.

    `curl -sS -X POST "$OD_DAEMON_URL/api/projects/$OD_PROJECT_ID/plugins/contribute-open-design" -H 'content-type: application/json' -d '{"path":"<plugin_context_path>"}'`

    Network access

    medium · line 11

    The documentation includes network, browsing, or remote request actions.

    `curl -sS -X POST "$OD_DAEMON_URL/api/projects/$OD_PROJECT_ID/plugins/contribute-open-design" -H 'content-type: application/json' -d '{"path":"<plugin_context_path>"}'`

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score66/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars91,167SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guidecatalog recordEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    nexu-io/open-design
    Skill path
    plugins/_official/examples/od-plugin-contribute-open-design/SKILL.md
    Commit
    edfa6b5f447e95cb120eae030f03baba00dc34de
    License
    Apache-2.0
    Collected
    2026-08-25
    Default branch
    main
    View the original SKILL.md

    Contribute Plugin to OpenDesign

    Use this workflow when the active project contains a copied plugin folder and the user wants to propose it for the OpenDesign community catalog.

    Workflow

    1. Read the active plugin inputs. plugin_context_path is the copied plugin folder relative to the project working directory.
    2. Inspect the copied plugin's manifest, skill instructions, examples, and compatibility metadata.
    3. Call the local daemon endpoint instead of hand-rolling GitHub commands: curl -sS -X POST "$OD_DAEMON_URL/api/projects/$OD_PROJECT_ID/plugins/contribute-open-design" -H 'content-type: application/json' -d '{"path":"<plugin_context_path>"}'
    4. Read the JSON response. If ok is true, report the PR URL, branch name when present in the log, and any useful validation summary.
    5. If the endpoint fails, report its message, code, and useful log lines. When authentication is missing, tell the user to run gh auth login --hostname github.com.

    Keep the pull request focused. Do not modify unrelated OpenDesign files unless a manifest validation issue requires a tiny supporting change.

    Frequently asked questions

    What to verify before installation and use

    How do I install od-plugin-contribute-open-design?

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

    Which permission-related actions were detected?

    Static rules flagged send-data, network in the source; the page lists the matching lines and excerpts.

    Alternatives

    Compare before choosing

    Computed 9858

    magnus919/agent-skills

    software-architecture-analysis

    Use this skill to reverse-engineer an existing software system, map its architecture, data flow, privacy posture, coupling, quality characteristics, and feature surface, then produce an evidence-grounded clean-room design document, PRD, or migration plan under new constraints. Use for codebase archaeology, implicit contract extraction, architecture health assessment, or decomposition-readiness analysis. Do not use for greenfield architecture design, direct code review, bug hunting, security audi

    Computed 9764

    Jamie-BitFlight/claude_skills

    standards-for-python-development

    Shared Python 3.11+ development standards covering type safety (ty, native generics, Protocol, TypeIs), layered architecture, error handling, performance, identifier naming, UI/CLI patterns (Rich/Typer), testing requirements (pytest, 80% coverage, TDD), and quality gates. Activates when any Python skill or agent needs to apply shared standards for implementation, code review, refactoring, or test authoring.

    Computed 9582

    mblode/agent-skills

    pr-reviewer

    Reviews the local diff or branch and returns a read-only, severity-tiered findings report. Modes cover standard bugs, structural quality, AI slop, and security audit. Use when asked to run /pr-reviewer, "review my changes", "code review", "thermo-nuclear review", "structural review", "deslop this", "clean up AI code", "security audit", "find vulnerabilities", or before commit, push, or handoff. For fixes use tidy; for PR creation use pr-creator; for CI or review comments use pr-babysitter; for f

    Computed 9425

    Borda/AI-Rig

    review

    Multi-agent code review of local Python files, directories, or the current git diff covering architecture, tests, performance, docs, lint, security, and API design. Scope: Python source files in local working tree. Python-file-free targets (pure JS/TS/Go/Rust projects) are out of scope. TRIGGER when: user asks to review local Python files, a directory, or the current git diff/working-tree changes, with no GitHub PR number involved; phrases: "review this", "review my changes", "code review this d