openwork-notary

Store Apple notarization credentials in macOS Keychain for OpenWork notarization workflows.

10|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/benjaminshafii/digital-empire --skill openwork-notary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openwork-notary
Source: https://github.com/benjaminshafii/digital-empire/tree/main/.opencode/skill/openwork-notary
Command: npx skills add https://github.com/benjaminshafii/digital-empire --skill openwork-notary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill securely stores Apple notarization credentials (issuer ID, key ID, and key path) in the macOS Keychain and uses them to streamline local OpenWork notarization workflows, reducing manual credential management.

Core Features & Use Cases

  • Secure credential storage and retrieval for Apple Notary tool workflows on macOS.
  • Support for retrieving issuer ID, key ID, and key path from Keychain during notarization steps.
  • Use case: Release a new OpenWork DMG by automatically performing notary history checks and stapling when credentials are available.

Quick Start

Follow these steps to set up and use the skill:

  • Ensure Keychain access is available and the OpenWork notary environment is configured.
  • Store credentials in Keychain: security add-generic-password -a issuer-id -s com.differentai.openwork.notary -w "<ISSUER_UUID>" -U security add-generic-password -a key-id -s com.differentai.openwork.notary -w "<KEY_ID>" -U security add-generic-password -a key-path -s com.differentai.openwork.notary -w "/path/to/AuthKey_<KEY_ID>.p8" -U
  • Read values during runtime: security find-generic-password -a issuer-id -s com.differentai.openwork.notary -w security find-generic-password -a key-id -s com.differentai.openwork.notary -w security find-generic-password -a key-path -s com.differentai.openwork.notary -w

Frequently Asked Questions about openwork-notary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I store Apple notarization credentials in macOS Keychain for automated workflows?

Store Apple notarization credentials in macOS Keychain by adding generic passwords for the issuer ID, key ID, and key path. This allows local OpenWork workflows to securely retrieve them during notary history checks and DMG stapling.

Do I need macOS Keychain access to run OpenWork notarytool workflows?

Yes, macOS Keychain access is required to securely store and retrieve the Apple notarization credentials. The workflow enforces credential retrieval from Keychain or environment variables and validates the key file before use.

How do I configure Apple notarytool credentials for a DMG release process?

Configure Apple notarytool credentials by adding the issuer ID, key ID, and AuthKey path as generic passwords in Keychain. The system reads these values at runtime to automate notarization submission and DMG stapling.

Can I use environment variables instead of Keychain for notarization credentials?

Yes, the notarization workflow enforces credential retrieval from either macOS Keychain or environment variables. It validates the key file before use, ensuring the notarytool submission proceeds securely regardless of the source.

What is the best way to secure Apple notarization keys for local release automation?

The best way to secure Apple notarization keys is storing the issuer ID, key ID, and key path in macOS Keychain. This reduces manual credential management and drives automated OpenWork notarization and DMG stapling.

Why does my OpenWork notarization workflow require a validated key file path?

The OpenWork notarization workflow validates the key file path to ensure the AuthKey is accessible before submitting to Apple. It retrieves this path from Keychain or environment variables to prevent errors during notarization.