build-dmg — Claude Code skill: signed macOS DMG from Xcode
build-dmg turns an Xcode project into a signed, distributable DMG: it resolves the scheme and team, then archives, exports and packages through a bundled script.
no license 135 installs ★ 5 updated 2026-08-31
npx skills add ulpi-io/skills --skill build-dmg -a claude-codeWhat build-dmg does
The skill takes a Mac app from Xcode project to a DMG you can hand out. It scans the repo first: app name, scheme, path to the .xcodeproj or .xcworkspace, any ExportOptions.plist, a VERSION file, signing hints already in place. Anything ambiguous gets a question before the build starts, not after it fails.
The work itself runs through helpers/build-dmg.sh from the project root: archive, export, packaging. APP_NAME and SCHEME are required; PROJECT, WORKSPACE, TEAM_ID, EXPORT_OPTIONS, USE_XCODEGEN, DMG_BACKGROUND and VERSION_FILE go in only when the project needs them. A project.yml means the project is regenerated with xcodegen generate first.
Signing is where it stays careful. It won't invent an identity, and ExportOptions.plist stays untouched without approval, since a bad export configuration ships something unsigned or aimed at the wrong distribution channel. With several schemes it asks which one to build. You get back the DMG path, app version and signing status; on failure you get the blocker category — signing, scheme, export options or the build itself.
What it helps with
- package a macOS app into a DMG without hand-writing xcodebuild steps
- pick the right scheme when the project has several
- regenerate the Xcode project with xcodegen before archiving
- tell a signing failure apart from an export-options failure
- get the DMG path and version after the build
Example prompts for the agent
- Build a DMG from this Xcode project
- Package the Mac app as a signed installer, scheme
MyApp - Run the build-dmg skill for
App.xcworkspace
How to install build-dmg
1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill build-dmg -a claude-code2Manually: put the files in place
~/.claude/skills/build-dmg/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/build-dmg/
1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill build-dmg -a codex2Manually: put the files in place
.agents/skills/build-dmg/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill build-dmg -a cursor2Manually: put the files in place
.cursor/skills/build-dmg/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ulpi-io/skills build-dmg2Manually: put the files in place
.github/skills/build-dmg/SKILL.md1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill build-dmg -a gemini-cli2Platform CLI
gemini skills install https://github.com/ulpi-io/skills --path build-dmgManually: put the files in place
.devin/skills/build-dmg/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill build-dmg -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about build-dmg
How do I install build-dmg in Claude Code?
Run npx skills add ulpi-io/skills --skill build-dmg -a claude-code. The skill lands at ~/.claude/skills/build-dmg/SKILL.md.
What does build-dmg do?
It builds a macOS app into a DMG: resolves the scheme and signing inputs, runs archive and export through helpers/build-dmg.sh, then packages the result. You get the DMG path, version and signing status.
What has to be set before a build?
APP_NAME and SCHEME are required, while variables such as TEAM_ID or EXPORT_OPTIONS are added only when needed. The skill never guesses a scheme, team ID or export options; it asks when something is unclear.