build-macos
Skill3 starsChanged 33 days agoMITView on GitHub
Build macOS apps (Harbor Clerk Server + Harbor Clerk) and report results. Optionally launch the server app.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- alembic/AGENTS.mdAGENTS.md
- frontend/AGENTS.mdAGENTS.md
- macos/AGENTS.mdAGENTS.md
- acceptanceSkill
- benchmarkSkill
- model-refreshSkill
- verifySkill
- harbor-clerkSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Run make apps in macos/ to build both macOS apps.
- Very specific: line 15
Check output for BUILD SUCCEEDED or BUILD FAILED / error: lines
- Very specific: line 25
If the user said "and run" or "and launch", open the server app: open macos/build/output/HarborClerkServer.app
- Very specific: line 28
If the build stops at configure: error: C compiler cannot create executables, the Command Line Tools SDK is newer than Xcode's linker.
≈ “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.
Files
Build macOS Apps
Run make apps in macos/ to build both macOS apps. Parse the output for
build success/failure and report a summary. All paths are relative to the
repository root.
Steps
- Run
(cd macos && make apps 2>&1) - Check output for
BUILD SUCCEEDEDorBUILD FAILED/error:lines - Report:
- Whether each app (HarborClerkServer, HarborClerk) built successfully
- Any build errors (show the actual error lines)
- App sizes from the "Server app" / "Client app" lines
- The
==> Versionline:package.shderives it fromgit describe(scripts/build-version.sh), so an untagged commit builds as<last tag> (<commits since>)and a dirty tree adds.dirtyto the stamp. Report it as printed; never "fix" it in the pbxproj (seedocs/releasing.md).
- If the user said "and run" or "and launch", open the server app:
open macos/build/output/HarborClerkServer.app
If the build stops at configure: error: C compiler cannot create executables,
the Command Line Tools SDK is newer than Xcode's linker; see the SDKROOT note
in macos/AGENTS.md. Signing (make sign) is never run by an agent.
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
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.

