robinebers/openusage · Archived

packaging-notarization

Prepare and troubleshoot packaging, signing, and notarization workflows for macOS distribution. Use when asked to archive a Mac app, validate bundle structure, reason about notarization readiness, or explain distribution-only failures.

Installation

$ npx skills add robinebers/openusage --skill packaging-notarization

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from robinebers/openusage · top by installs.

npx skills add robinebers/openusage

Browse all from robinebers/openusage

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 3.9K
License LICENSE
Default branch main
Open issues 50
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,529 B
  • docs SUMMARY.md 265 B

History

  1. First recorded snapshot · 1 installs

SKILL.md

Packaging & Notarization

Quick Start

Use this skill when the work is about shipping the app rather than merely running it locally: archives, exported app bundles, notarization readiness, hardened runtime, or distribution validation.

Workflow

  1. Confirm the distribution goal.

- Local archive validation - Signed distributable app - Notarization troubleshooting

  1. Inspect the artifact.

- Validate app bundle structure. - Check nested frameworks, helper tools, and entitlements.

  1. Inspect signing and runtime prerequisites.

- Hardened runtime - Signing identity - Nested code signatures - Required entitlements

  1. Explain notarization readiness or failure.

- Separate packaging issues from trust-policy symptoms. - Point to the minimum follow-up validation commands.

Guardrails

  • Do not present notarization as required for ordinary local debug runs.
  • Call out when you lack the actual exported artifact and are inferring from project settings.
  • Keep advice concrete and verifiable.

Output Expectations

Provide:

  • what artifact or settings were inspected
  • whether the app looks distribution-ready
  • the top missing prerequisite or failure mode
  • the next validation or repair step