How do I install the Omd:update skill?

Run npx skillmds@latest add kwakseongjae/omd-update-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Omd:update safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Omd:update?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Omd:update free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Omd:update?

kwakseongjae (@kwakseongjae) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Omd:update by kwakseongjae — Agent Skill

Name: Omd:update
Author: kwakseongjae

Omd:update

Safely update an existing oh-my-design installation in place and verify it afterward. Use when the user asks to update, upgrade, refresh, reinstall, or check whether their OmD skills, agents, hooks, or reference catalog are current.

kwakseongjae Updated Sep 17, 2026

File contents

Update oh-my-design

Update only the OmD installation the user already has. Preserve its project/global scope, installed channels, Cursor compatibility mode, DESIGN.md, references added by the user, and every file outside OmD ownership.

Workflow

Run from the intended project root unless the user explicitly requests the global installation.
Use the latest package as the executor:
```
npx oh-my-design-cli@latest update
```
For a global installation, append --global. For another project root, append --dir <path>.
Never add --force. The update command detects installed channels, preserves the existing scope, refreshes managed files, and runs the equivalent of a post-update doctor check.
If the command reports a protected local difference, stop. Show the exact scoped repair command or manual action it prints; do not overwrite the file on the user's behalf.
Report the before/after state, preserved scope and channels, and any skipped drift. Do not claim success if the exit code is non-zero.
Tell the user to restart the coding agent, then run:

npx oh-my-design-cli@latest doctor --self-test


## Safety contract

- Do not switch project ↔ global scope.
- Do not install channels that were not already installed.
- Do not enable proof policy, hooks, or Cursor Agent Skills that were previously absent.
- Do not update deprecated MCP configuration.
- Do not use `--force`, delete drifted files, or replace symlinks automatically.
- Do not edit `DESIGN.md` or product files during an OmD update.

If no installation exists, explain that this is a fresh install and use `npx oh-my-design-cli@latest` only after the user confirms installation intent.

---name: omd-update-2description: Safely update an existing oh-my-design installation in place and verify it afterward. Use when the user asks to update, upgrade, refresh, reinstall, or check whether their OmD skills, agents, hooks, or reference catalog are current.---# Update oh-my-designUpdate only the OmD installation the user already has. Preserve its project/global scope, installed channels, Cursor compatibility mode, `DESIGN.md`, references added by the user, and every file outside OmD ownership.## Workflow1. Run from the intended project root unless the user explicitly requests the global installation.2. Use the latest package as the executor: ```bash npx oh-my-design-cli@latest update ``` For a global installation, append `--global`. For another project root, append `--dir <path>`.3. Never add `--force`. The update command detects installed channels, preserves the existing scope, refreshes managed files, and runs the equivalent of a post-update doctor check.4. If the command reports a protected local difference, stop. Show the exact scoped repair command or manual action it prints; do not overwrite the file on the user's behalf.5. Report the before/after state, preserved scope and channels, and any skipped drift. Do not claim success if the exit code is non-zero.6. Tell the user to restart the coding agent, then run: ```bash npx oh-my-design-cli@latest doctor --self-test ```## Safety contract- Do not switch project ↔ global scope.- Do not install channels that were not already installed.- Do not enable proof policy, hooks, or Cursor Agent Skills that were previously absent.- Do not update deprecated MCP configuration.- Do not use `--force`, delete drifted files, or replace symlinks automatically.- Do not edit `DESIGN.md` or product files during an OmD update.If no installation exists, explain that this is a fresh install and use `npx oh-my-design-cli@latest` only after the user confirms installation intent.

Frequently asked questions