kkrafft1999/snotra / .claude/skills/install
install
VerifiedBuilds Snotra Agent locally (electron-forge package, macOS/arm64) and replaces the installed app at /Applications/Snotra Agent.app with the fresh build. Triggers on sentences like "bau die App und kopier sie nach Programme", "installier die App lokal", "App neu bauen und installieren", "lokalen Build nach Applications", "build the app and copy it to Applications", "install the app locally", "rebuild and install the app". Only makes sense in this repository (snotra) and on an Apple Silicon Mac.
Build the app locally and install it into Applications
This skill produces a local, unsigned build and replaces the installed app with it. Nothing is committed, pushed or published.
Step 1 — pre-flight (brief, without asking)
- Make sure Node is ≥ 24 (
node -v). Usually the shell already provides v24 through nvm. If it doesn't, put the nvm path in front of every bash call:
(If that version doesn't exist:export PATH="$HOME/.nvm/versions/node/v24.18.1/bin:$PATH"ls ~/.nvm/versions/node/and take the newest v24.) Experience says a wrong version comes from an absoluteexport PATH=...line in~/.zshrcthat some tool wrote there. Mention that to the user briefly. - Is the app running right now?
pgrep -x "Snotra Agent". If it is, don't ask the user — point out after copying that they have to restart the old instance. Only quit it (osascript -e 'quit app "Snotra Agent"') if the user explicitly wants that. - Uncommitted changes are allowed. That is exactly what the local build is for: trying out a state before committing it. Mention briefly that the build contains the working state, uncommitted changes included.
Step 2 — build
npm run package
npm run package (see package.json) first syncs the renderer vendor files and
then calls electron-forge package --arch arm64 --platform darwin. The result:
out/Snotra Agent-darwin-arm64/Snotra Agent.app
On errors, stop and show the relevant output. Don't delete node_modules or run
npm install on suspicion. Only suggest npm install once the error message
points clearly at missing dependencies.
Step 3 — install
rm -rf "/Applications/Snotra Agent.app" && cp -R "out/Snotra Agent-darwin-arm64/Snotra Agent.app" /Applications/
The deletion only affects the copy of the app bundle in /Applications, no user
data (the settings live in ~/Library/Application Support/). No confirmation
needed, therefore.
Until #795 the app was called Snotra AI. If /Applications/Snotra AI.app is
still there, it is the same app under its old name: remove it as well
(rm -rf "/Applications/Snotra AI.app"), otherwise two copies sit side by
side. Its data is not in the bundle and stays — the folder is
~/Library/Application Support/Snotra AI, named after the platform.
Step 4 — verify and report
/usr/libexec/PlistBuddy -c 'Print :CFBundleShortVersionString' "/Applications/Snotra Agent.app/Contents/Info.plist"
Report briefly: the installed version, the git commit of the build
(git rev-parse --short HEAD, plus a note "with uncommitted changes" when
git status --porcelain isn't empty), and whether a running instance has to be
restarted. Only start the app (open -a "Snotra Agent") when the user asked for
that.
Notes
- The build is unsigned. Gatekeeper may complain on first launch. That is
expected (stage 1, see
docs/release/release.md). - For a published release there is the separate
releaseskill. This skill does not replace it. - A Windows build (
npm run package:win) is not part of this skill.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |