packaging-notarization

Prepare macOS packaging and notarization workflows. Use when archiving apps, validating bundles, or explaining distribution-only failures.

Jump to install Review files

Repository: openai/plugins
Last source activity: May 27, 2026 at 14:26
Detected SKILL.md language: English
Stars: 7,454
Forks: 970

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with an AI assistant

Copy this prompt into the AI assistant you're using.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/openai/plugins/tree/main/plugins/build-macos-apps/skills/packaging-notarization.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/openai/plugins --skill packaging-notarization

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

name: packaging-notarization
description: Prepare macOS packaging and notarization workflows. Use when archiving apps, validating bundles, or explaining distribution-only failures.

# 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 2. Inspect the artifact. - Validate app bundle structure. - Check nested frameworks, helper tools, and entitlements. 3. Inspect signing and runtime prerequisites. - Hardened runtime - Signing identity - Nested code signatures - Required entitlements 4. 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

View on GitHub

Back to search Back to installation

assess-patch-risk

Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility. Use for generated patch files, provider pull-request diffs, or commit ranges when reviewers need evidence about affected runtime paths, contracts, tests, and recoverability. This skill is read-only and does not generate, edit, apply, push, or merge the patch.

2026-10-08

deep-security-scan

Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide or scoped-path Codex Security scan. Run repeated complete independent Standard scans with the Codex Security deep-scan tool, which aggregates their validated findings and prepares the canonical artifacts; then complete the same scan once. Do not use for PRs, commits, branch diffs, or working-tree diffs.

2026-10-08

finding-discovery

Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.

2026-10-08

View all from this repository

packaging-notarization

Source facts

Install options

Install with an AI assistant

Review the source files

More from this repository

Install with an AI assistant

More from this repository