AgentStack
SKILL verified MIT Self-run

Macos Signing Inspector

skill-xopoko-build-swift-apps-macos-signing-inspector · by Xopoko

Use when an existing macOS app or binary needs code-signing, entitlement, hardened runtime, sandbox, Gatekeeper, or trust-policy diagnosis. Not for full distribution packaging or running notarization submissions.

No reviews yet
0 installs
11 views
0.0% view→install

Install

$ agentstack add skill-xopoko-build-swift-apps-macos-signing-inspector

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Macos Signing Inspector? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

macOS Signing Inspector

Quick Start

Use this skill when the failure smells like codesigning rather than compilation: launch refusal, missing entitlement, invalid signature, sandbox mismatch, hardened runtime confusion, or trust-policy rejection.

Use macos-notarization-packager when the goal is a distributable notarized artifact. Use appstore-notary-runner when the next step is executing asc notarization submit/status/log/staple commands.

Workflow

  1. Inspect the bundle or binary.
  • Locate the .app or executable.
  • Identify the main binary inside Contents/MacOS/.
  1. Read signing details.
  • Use codesign -dvvv --entitlements :- .
  • Use spctl -a -vv when Gatekeeper behavior matters.
  • Use plutil -p for entitlements or Info.plist inspection.
  1. Classify the failure.
  • Unsigned or ad hoc signed
  • Wrong identity
  • Entitlement mismatch
  • Hardened runtime issue
  • App Sandbox issue
  • Nested code signing issue
  • Distribution/notarization prerequisite issue
  1. Explain the minimum fix path.
  • Say exactly what is wrong.
  • Show the shortest set of validation or repair commands.
  • Distinguish local development problems from distribution problems.

Useful Commands

  • codesign -dvvv --entitlements :-
  • spctl -a -vv
  • security find-identity -p codesigning -v
  • plutil -p

Guardrails

  • Never invent missing entitlements.
  • Do not conflate notarization with local debug signing.
  • If the real issue is a build setting or provisioning profile, say so directly.

Output Expectations

Provide:

  • what artifact was inspected
  • what signing state it is in
  • the exact failure class
  • the minimum fix or validation sequence

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.