agentleFS
kkrafft1999kkrafft1999/snotra/.claude/skills/install/SKILL.md

install

Skill6 starsChanged 10 days agoApache-2.0View on GitHub

Builds 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.

  • Deletes or force-pushes

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use update.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    update

    Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Make sure Node is ≥ 24 (node -v).

    line 20
  2. Very specific:

    Only quit it (osascript -e 'quit app "Snotra Agent"') if the user explicitly wants that.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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)

  1. 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:
    export PATH="$HOME/.nvm/versions/node/v24.18.1/bin:$PATH"
    (If that version doesn't exist: ls ~/.nvm/versions/node/ and take the newest v24.) Experience says a wrong version comes from an absolute export PATH=... line in ~/.zshrc that some tool wrote there. Mention that to the user briefly.
  2. 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.
  3. 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 release skill. This skill does not replace it.
  • A Windows build (npm run package:win) is not part of this skill.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.