Scraps Review
getsentry/sentry
Filter large Sentry Scraps design-system migration PRs for review by separating mechanical import-path changes, generated baseline updates, snapshot mocks, and pure renames from substantive…
Run or assist a release in any MUI repo, at any stage - release PR, npm publish, docs deploy, GitHub release.
$ npx skills add mui/mui-public --skill mui-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mui/mui-public mui-release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mui/mui-public.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/mui-release .claude/skills/mui-release && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "mui-release" agent skill from https://github.com/mui/mui-public/tree/master/skills/mui-release into .claude/skills/mui-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mui-release", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mui/mui-public/tree/master/skills/mui-releaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mui/mui-public --skill mui-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mui/mui-public mui-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mui/mui-public.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/mui-release .agents/skills/mui-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mui-release" agent skill from https://github.com/mui/mui-public/tree/master/skills/mui-release into .agents/skills/mui-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mui-release", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mui/mui-public --skill mui-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mui/mui-public mui-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mui/mui-public.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/mui-release .cursor/skills/mui-release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "mui-release" agent skill from https://github.com/mui/mui-public/tree/master/skills/mui-release into .cursor/skills/mui-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mui-release", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mui/mui-public.git --path skills/mui-release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mui/mui-public --skill mui-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mui/mui-public mui-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mui/mui-public.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/mui-release .gemini/skills/mui-release && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "mui-release" agent skill from https://github.com/mui/mui-public/tree/master/skills/mui-release into .gemini/skills/mui-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mui-release", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mui/mui-public mui-releaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mui/mui-public --skill mui-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mui/mui-public.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/mui-release .github/skills/mui-release && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "mui-release" agent skill from https://github.com/mui/mui-public/tree/master/skills/mui-release into .github/skills/mui-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mui-release", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mui/mui-public --skill mui-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mui/mui-public mui-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mui/mui-public.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/mui-release .opencode/skills/mui-release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "mui-release" agent skill from https://github.com/mui/mui-public/tree/master/skills/mui-release into .opencode/skills/mui-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mui-release", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
mui-releaseRun or assist a release in any MUI repo, at any stage - release PR, npm publish, docs deploy, GitHub release.
Mui Release is an agent skill from mui/mui-public. Run or assist a release in any MUI repo, at any stage - release PR, npm publish, docs deploy, GitHub release.
Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `stage-1-prepare-pr.md`, `stage-2-publish-packages.md` and `stage-3-publish-docs.md`).
It sits in Frontend & Design, covering Design systems. It works with npm and GitHub. The repository describes itself as: The public mono-repository of MUI (as an organization), see mui/mui-private for the opposite. The licence is MIT.
Read from SKILL.md and the folder at commit 6229b33. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
ghnpmcurlFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use gh, npm and curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Mui Release loads about 749 tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 227 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from mui/mui-public at commit 6229b33, republished under its MIT licence (© mui). 227 words, ~749 tokens.
.claude/skills/mui-release/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.Every MUI repo releases through the same staged pipeline. Each stage depends on the previous one completing — never start a stage before its predecessor is done. This skill describes the shared skeleton; the details vary per repo.
Resumable: the skill can be invoked at any stage — a release often spans multiple sessions (e.g. the PR was created and merged earlier, and the user now wants to trigger the npm publish). In the pipeline diagram below, each arrow out of a stage states the observable evidence that the stage is complete: resume at the first stage whose evidence is missing. Confirm the detected stage with the user before continuing; earlier stages' outputs are inputs, not work to redo.
Source of truth: the target repo's scripts/README.md is the authoritative, evolving runbook. Always read it in the target checkout before releasing; use this skill to know what the stages mean and what to expect. Where the README contradicts this skill, the README wins. Repo-specific steps (docs release pages, hotfix flows, prerelease progressions, docs-only deploys, first-time package publishing) live only there. Repos without that runbook: read their release workflow directly.
Each stage's instructions live in its own file — after detecting and confirming the current stage, read that stage's file:
flowchart TD
S1["Stage 1: Prepare the release PR\n(stage-1-prepare-pr.md)"]
S2["Stage 2: Merge the PR, then publish\n(stage-2-publish-packages.md)"]
S3["Stage 3: Publish the docs\n(stage-3-publish-docs.md)"]
S4["Stage 4: Publish the GitHub release, then announce\n(stage-4-github-release.md)"]
S1 -- "open PR with the release label,\napproved, CI green" --> S2
S2 -- "release PR merged, packages on npm at\nthe new version, draft GitHub release created" --> S3
S3 -- "docs live for the new version" --> S4
S4 -- "published non-draft GitHub release for the\ncurrent root package.json version\n(release done, next one starts at Stage 1)" --> S1Verify each stage's evidence with read-only commands (run in the target checkout; <version> is the root package.json version):
# release PR: open (stage 1) or merged (stage 2 done merging)
gh pr list --label release --state open --json number,title,reviewDecision
gh pr list --label release --state merged --limit 1 --json number,title,mergedAt
gh pr checks <number> # CI green?
# packages on npm at the new version
npm view <main-package>@<version> version
# GitHub release: exists? still a draft?
gh release list --limit 5 --json tagName,isDraft,isLatest
gh release view "v<version>" --json tagName,isDraft
# docs live for the new version
curl -s <docs-url> | grep "<version>" # or check the Netlify dashboard© mui, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files in skills/mui-release of mui/mui-public.
Open the folder on GitHubat commit 6229b33
Mui Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Mui Release this skillmui/mui-public | 106 | — | ~749 | Automated safety check: Pass | MIT | |
| Scraps Reviewgetsentry/sentry | 45k | — | ~1.2k | Automated safety check: Notes | Custom licence | |
| Run Umbraco UIumbraco/Umbraco.UI | 152 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Design SystemBuildGreatProducts/builder-os | 227 | — | ~4.8k | Automated safety check: Pass | MIT | |
| Plugin InstallerIgorWarzocha/Opencode-Workflows | 122 | — | ~1.3k | Automated safety check: Pass | None | |
| Design Project Scaffoldplugin87/ux-ui-agent-skills | 1.5k | — | ~1.1k | Automated safety check: Pass | MIT |
getsentry/sentry
Filter large Sentry Scraps design-system migration PRs for review by separating mechanical import-path changes, generated baseline updates, snapshot mocks, and pure renames from substantive…
umbraco/Umbraco.UI
Build, run, and drive the Umbraco.UI (UUI) web-component library via its Storybook.
BuildGreatProducts/builder-os
Translates an image (or a set of image references — screenshots, mockups, Figma URLs, live websites) into two mirrored design-system artifacts: docs/design.md (YAML tokens + prose, following…
IgorWarzocha/Opencode-Workflows
Find, install, and configure OpenCode plugins from the catalog or community.
plugin87/ux-ui-agent-skills
Creates a new design-product project from the kit's product-design template, then installs the engine folders and the Playwright dependency that the quality gates need.
muratgur/ordinus
Work with shadcn/ui in Ordinus. An agent skill from muratgur/ordinus.
mui/mui-public
Fetch a deterministic snapshot of open MUI Renovate PRs and review them one by one.
mui/mui-public
Triage MUI GitHub issues from a mui/<repo/issues/<num URL or issue number - fetch context, classify state/type labels, prepare a durable summary comment, and emit a reviewable apply script without…
mui/mui-public
Review the current diff for regressions, correctness bugs, tests, simplifications, and docs issues, scaling depth to a low/medium/high/xhigh/max effort level.
mui/mui-public
Fix a Renovate dependency-update PR with the minimal compatible code adaptation, extracting a dependency bump from a grouped PR only when the fix requires the new version.
Categories
Run or assist a release in any MUI repo, at any stage - release PR, npm publish, docs deploy, GitHub release. Mui Release is an agent skill from mui/mui-public. Run or assist a release in any MUI repo, at any stage - release PR, npm publish, docs deploy, GitHub release.
Mui Release fits situations like: tasks that involve Design systems.
Run `npx skills add mui/mui-public --skill mui-release -a claude-code`. Or copy the skill folder (skills/mui-release in mui/mui-public) into .claude/skills/mui-release in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mui/mui-public --skill mui-release -a codex`. Or copy the skill folder (skills/mui-release in mui/mui-public) into .agents/skills/mui-release in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mui/mui-public --skill mui-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mui-release, .gemini/skills/mui-release, .github/skills/mui-release and .opencode/skills/mui-release in your project.
Going by SKILL.md and its folder, Mui Release needs the command-line tools its instructions call (gh, npm and curl).
SKILL.md contains no URLs. Its commands use gh, npm and curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Mui Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 749 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Mui Release: Scraps Review (getsentry/sentry, 45k stars), Run Umbraco UI (umbraco/Umbraco.UI, 152 stars), Design System (BuildGreatProducts/builder-os, 227 stars) and Plugin Installer (IgorWarzocha/Opencode-Workflows, 122 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mui (a GitHub organization) maintains it in mui/mui-public, which has 106 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 7, 2026.
Source: mui/mui-public on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.