agentleFS
jamesblackwelljamesblackwell/falcondeck/.agents/skills/desktop-mac-release/SKILL.md

desktop-mac-release

Skill7 starsChanged 8 days agoMITView on GitHub

Cut, watch, and publish a signed notarized FalconDeck Mac GitHub Release (DMG). Use when asked to ship, release, tag, or publish the Mac/desktop app, a desktop-v* tag, a downloadable DMG, or GitHub Releases for desktop.

  • Reads credentials
  • Commits and pushes

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read docs/13-desktop-updates.md for signing setup, secrets, updater wiring, and troubleshooting.

    line 8
  2. Distinctive:

    Do not ship an unsigned zip.

    line 10
  3. Distinctive:

    Do not include unrelated dirty work.

    line 17
  4. Very specific:

    If this is not a retag of an unpublished draft, bump Cargo.toml and run npm run desktop:version:sync.

    line 21
  5. Very specific:

    Do not pass APPLE_ID / APPLE_PASSWORD into tauri-action unless those secrets are actually set.

    line 34
  6. Very specific:

    Never commit .p12, .p8, or updater private keys.

    line 37
  7. Distinctive:

    If secrets are missing, stop.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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

Desktop Mac release

Read docs/13-desktop-updates.md for signing setup, secrets, updater wiring, and troubleshooting. This skill is the agent procedure.

Do not ship an unsigned zip. Gatekeeper blocks internet-downloaded Mac apps that are not Developer ID–signed and notarized.

Preconditions

  • GitHub Actions secrets already exist (names only via gh secret list): APPLE_CERTIFICATE, APPLE_CERTIFICATE_PASSWORD, APPLE_TEAM_ID, APPLE_API_ISSUER, APPLE_API_KEY, APPLE_API_KEY_P8, TAURI_SIGNING_PRIVATE_KEY, TAURI_SIGNING_PRIVATE_KEY_PASSWORD, FALCONDECK_UPDATER_PUBLIC_KEY.
  • Workflow is release-desktop.yml: macOS Apple Silicon + Intel only.
  • Canonical version is [workspace.package].version in Cargo.toml. Tag must be desktop-v plus that version.
  • Do not include unrelated dirty work. Do not rewrite a tag that already has a published GitHub Release.

Cut a release

  1. If this is not a retag of an unpublished draft, bump Cargo.toml and run npm run desktop:version:sync.
  2. Push the intended main.
  3. git tag desktop-vX.Y.Z && git push origin desktop-vX.Y.Z (creates a draft release).
  4. Watch both publish-tauri jobs. Use scripts/watch-release.sh <run-id> plus the long-running-background-tasks monitor tool. Do not poll in the agent loop.
  5. Confirm the draft has FalconDeck_*_aarch64.dmg, FalconDeck_*_x64.dmg, FalconDeck_{aarch64,x64}.app.tar.gz plus .sig, and latest.json with darwin-aarch64 and darwin-x86_64.
  6. Download both DMGs from the draft (not make desktop-install). Tauri notarizes the .app, then signs the DMG with no ticket. Submit each DMG with notarytool, stapler staple it, and gh release upload --clobber the versioned DMGs plus the FalconDeck_{aarch64,x64}.dmg aliases. stapler validate must succeed, and spctl --assess --type open --context context:primary-signature must report Notarized Developer ID. Then confirm the app inside: daemon starts, and one real Codex or Claude turn works.
  7. gh release edit desktop-vX.Y.Z --draft=false.
  8. Point README (and site copy if it still says “coming soon”) at the release URL.

Return the release URL. Use the ntfy skill when CI was long or James asked to be notified.

Fragile rules

  • Do not pass APPLE_ID / APPLE_PASSWORD into tauri-action unless those secrets are actually set. Empty strings make Tauri use Apple-ID auth and notarization returns 401.
  • Packaged builds use npm run build:frontend (Vite). npm run build / tsc -b is not the release gate.
  • ObjC @available needs libclang_rt.osx linked from apps/desktop/src-tauri/build.rs. Missing it fails release link with ___isPlatformVersionAtLeast.
  • Never commit .p12, .p8, or updater private keys. Local copies live under ~/.tauri/; Doppler project falcondeck / prd is the backup.

First-time signing

If secrets are missing, stop. Account Holder creates a Developer ID Application cert (not iOS/App Store Distribution). Steps are in docs/13. Do not invent credentials.

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.