od-contribute
One-click contribution flow for Open Design (nexu-io/open-design) — even for non-coders. Pick one of four cards (ship a Skill or Design System you made with OD; translate docs; fix a typo / write a blog; report a bug), the agent validates and opens a PR (or issue) for you. Trigger words contribute to open design, ship my OD skill, ship my OD design system, translate OD docs, report an OD bug, od-contribute.
Profile →npx skills add nexu-io/open-design --skill od-contribute --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# od-contribute — first-contribution flow for Open Design Locked to `nexu-io/open-design`. Branches by **contribution type**, not by issue. Replaces the dev-loop with type-specific no-code validators. Designed so a product user with zero coding background can ship a real PR. ## Language Mirror the user's language in every user-facing message — `AskUserQuestion` labels and descriptions, status updates, error explanations. Detect from their first message; when uncertain, default to English. **Generated artifacts (PR titles, commit messages, PR/issue body files, branch names) MUST be English** regardless of the user's chat language. GitHub conventions, maintainer review, and search all assume English. The templates under `templates/` are already English — keep them that way when rendering. Scripts live under `scripts/`. Source the shared helpers from any script: ```bash source "$(dirname "$0")/config.sh" ``` `SKILL_DIR` below = the directory that contains this `SKILL.md`. --- ## Step 1 — Prereq check (always first) ```bash bash "$SKILL_DIR/scripts/check-prereqs.sh" ``` - Exit 0: capture `GH_USER=<login>` from stdout. Default `TARGET_FORK="${GH_USER}/open-design"`. - Exit 2: surface th
- Language
- Step 1 — Prereq check (always first)
- Step 2 — Pick contribution type
- Step 3a — OD product submission (Skill / Design System)
- Step 3b — i18n translation
- Step 3c — Docs / blog / typo
- Step 3d — Bug report (issue path, no PR)
- Step 7 — Preview + confirm (shared, PR branches only)
- Step 8 — Push & open PR
- Safety rails (mandatory)
- When NOT to use this skill
source "$(dirname "$0")/config.sh" bash "$SKILL_DIR/scripts/check-prereqs.sh" Design System: file matching DESIGN.md anatomy. bash "$SKILL_DIR/scripts/setup-workspace.sh" skill <slug> or bash "$SKILL_DIR/scripts/setup-workspace.sh" design-system <slug> bash "$SKILL_DIR/scripts/validate-skill-submission.sh" "$WORKDIR/skills/<slug>" bash "$SKILL_DIR/scripts/validate-design-system.sh" \ bash "$SKILL_DIR/scripts/setup-workspace.sh" i18n translate capture WORKDIR
What does the od-contribute skill do?
One-click contribution flow for Open Design (nexu-io/open-design) — even for non-coders. Pick one of four cards (ship a Skill or Design System you made with OD; translate docs; fix a typo / write a blog; report a bug), the agent validates and opens a PR (or issue) for you. Trigger words contribute to open design, ship my OD skill, ship my OD design system, translate OD docs, report an OD bug, od-contribute.
How do I install it?
Run `npx skills add nexu-io/open-design --skill od-contribute --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.