build-macos-tray

Builds, smoke-tests, and installs the macOS tray app while logging structured findings.

5|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/8007342/tillandsias --skill build-macos-tray-8007342
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-macos-tray
Source: https://github.com/8007342/tillandsias/tree/main/skills/build-macos-tray
Command: npx skills add https://github.com/8007342/tillandsias --skill build-macos-tray-8007342

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running a full macOS build of the tillandsias tray app manually is error-prone and leaves no shared record, so sibling Linux and Windows hosts cannot tell whether the macOS build is green or what regressed. ## Core Features & Use Cases - Full build cycle: Runs scripts/build-macos-tray.sh, verifies the binary embeds the current HEAD git SHA, and checks codesign and tarball artifacts. - Autonomous smoke testing: Launches the tray binary detached, validates --diagnose --json exit codes, and tests clean SIGTERM shutdown without user clicks, including a minimal-PATH LaunchServices simulation. - Structured findings log: Appends a greppable section per run to plan/issues/macos-build-findings-<DATE>.md with a fixed SECTION_KIND taxonomy, then commits and pushes per branch policy. - Use Case: A daily unattended loop invokes this skill on the osx-next host so the whole team sees whether the macOS tray build passed, failed, or regressed, with concrete next-step asks when it did not. ## Quick Start Run the build-macos-tray skill on the macOS Apple Silicon host to build the tray app, smoke-test it, install it locally, and record the findings.

Frequently Asked Questions about build-macos-tray

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an unattended macOS build and smoke test for a tray app?▼

Invoke this skill on the macOS host: it runs scripts/build-macos-tray.sh, verifies the binary embeds the current HEAD SHA, launches the app detached, checks --diagnose --json exit codes, and installs to ~/Applications atomically.

How do I test a macOS menubar app without clicking the UI?▼

Launch the binary detached in the background, wait three seconds, then send SIGTERM and confirm a clean exit. The skill also runs --diagnose --json, where exit 0 or 2 is acceptable and exit 1 signals a hard failure.

Why does a macOS app behave differently when launched from Finder versus a terminal?▼

LaunchServices-started apps get a minimal PATH of /usr/bin:/bin:/usr/sbin:/sbin, while terminal launches inherit your shell environment. The skill reproduces the GUI regime with env -i and verifies the live process PATH with ps eww.

Does this build skill work on Linux or Windows hosts?▼

No, it must run on macOS Apple Silicon, specifically the osx-next worker host. Its findings file exists precisely so Linux and Windows hosts can see macOS build status without running the build themselves.

What happens when the macOS tray build fails mid-run?▼

The skill stops at the failing stage and still writes a findings entry with an appropriate SECTION_KIND such as build-failed, diagnose-hard-failure, launch-failed, quit-hung, or install-corrupted, plus a next-iteration ask.