agentleFS
OutThisLifeOutThisLife/brooklyn-skills/skills/notarize-mac/SKILL.md

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.

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
  1. Distinctive:

    Use the project's existing notarization automation.

    line 11
  2. Distinctive:

    use a path the user supplies first.

    line 19
  3. Distinctive:

    if none exists, ask for its location instead of recreating it.

    line 21
  4. Distinctive:

    Run the script from the environment it expects.

    line 22
  5. Very specific:

    Verify the resulting artifact with the script's checks or spctl.

    line 25
  6. Distinctive:

    Never print private key contents, signing credentials, or secret values.

    line 28

≈ “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.

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

Notarize macOS Build

Use the project's existing notarization automation. Don't invent a new signing pipeline or expose credentials.

Procedure

  1. Confirm the checkout and branch. Default to a clean, current default branch.
  2. Locate the existing notarization/release script (e.g. a notarize-*-installer.sh or 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.
  3. Run the script from the environment it expects.
  4. Preserve its signing identity, App Store Connect key handling, artifact naming, and notarization flow.
  5. Verify the resulting artifact with the script's checks or spctl.
  6. Report the artifact path, size, notarization result, and Gatekeeper result.

Never print private key contents, signing credentials, or secret values.

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.