notarize-mac
Skill207 starsChanged 4 months agoMITView on GitHub
Build and verify a signed, notarized macOS app or DMG using the project's existing notarization automation. Use when the user asks to notarize a Mac build, produce a release DMG, or verify Gatekeeper.
In this repository22 other files it gives its agents.
- audit-onlySkill
- babysitSkill
- cleanSkill
- cprSkill
- draft-tweetSkill
- engraved-figuresSkill
- free-disk-spaceSkill
- list-open-workSkill
- no-tropesSkill
- perfSkill
- pr-readySkill
- pr-triageSkill
- pr-updateSkill
- researchSkill
- runtime-debugSkill
- stacked-prSkill
- ticket-shipSkill
- triageSkill
- ui-onlySkill
- ui-systemSkill
- visual-verifySkill
- workSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use the project's existing notarization automation.
- Distinctive: line 19
use a path the user supplies first.
- Distinctive: line 21
if none exists, ask for its location instead of recreating it.
- Distinctive: line 22
Run the script from the environment it expects.
- Very specific: line 25
Verify the resulting artifact with the script's checks or spctl.
- Distinctive: line 28
Never print private key contents, signing credentials, or secret values.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Notarize macOS Build
Use the project's existing notarization automation. Don't invent a new signing pipeline or expose credentials.
Procedure
- Confirm the checkout and branch. Default to a clean, current default branch.
- Locate the existing notarization/release script (e.g. a
notarize-*-installer.shor the release script the project already ships):- use a path the user supplies first;
- otherwise search the repo and nearby release/notary checkouts;
- if none exists, ask for its location instead of recreating it.
- Run the script from the environment it expects.
- Preserve its signing identity, App Store Connect key handling, artifact naming, and notarization flow.
- Verify the resulting artifact with the script's checks or
spctl. - Report the artifact path, size, notarization result, and Gatekeeper result.
Never print private key contents, signing credentials, or secret values.
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.

