via54macfix

Diagnose and fix macOS Gatekeeper and launchd failures for Go binaries.

1|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/veawho/via54Skills --skill via54macfix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: via54macfix
Source: https://github.com/veawho/via54Skills/tree/main/via54macfix
Command: npx skills add https://github.com/veawho/via54Skills --skill via54macfix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves common macOS failures when installing or running native binaries, including Gatekeeper blocks, provenance extended attributes, launchd throttling, and incorrect user-domain bootstrapping.

Core Features & Use Cases

  • Gatekeeper Diagnostics: Identify spctl, quarantine, ownership, and installation-path problems affecting unsigned or locally built binaries.
  • Launchd Troubleshooting: Diagnose silent child-process failures, bootstrap I/O errors, restart throttling, and incorrect system versus GUI user domains.
  • Safe Operational Guidance: Provides command-based verification, recommended installation paths, launchd configuration patterns, cooldown procedures, and post-fix checklists for Go binaries and related daemons.
  • Use Case: When a Go-based Feishu bot runs successfully from the terminal but fails under launchd on macOS Sequoia, use this Skill to inspect extended attributes, identify the launchd domain or throttle state, and select a reliable foreground or wrapper-based deployment.

Quick Start

Use the via54macfix skill to diagnose why my native macOS binary or launchd service fails and provide the safest verified fix.

Frequently Asked Questions about via54macfix

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

FAQPage Schema
Why does my Go binary run in terminal but fail under launchd on macOS Sequoia?

A Go binary may fail under launchd due to Gatekeeper blocks, quarantine extended attributes, or launchd throttling. Diagnose the failure by inspecting extended attributes with xattr and checking the launchd domain or throttle state before selecting a wrapper-based deployment.

How do I fix Gatekeeper blocks on unsigned macOS binaries?

To fix Gatekeeper blocks on unsigned macOS binaries, identify spctl assessment issues, quarantine extended attributes, and installation-path problems. Verify the binary's provenance using spctl and xattr, then apply the recommended installation paths and command-based verification procedures.

How do I stop launchd throttling and silent child-process failures for native daemons?

Stop launchd throttling and silent child-process failures by diagnosing bootstrap I/O errors and verifying the correct system versus GUI user service domains. Use launchctl and log commands to inspect the throttle state and apply cooldown procedures before restarting the daemon.

Do I need to remove quarantine extended attributes before deploying a native macOS daemon?

You need to remove quarantine extended attributes before deploying a native macOS daemon to prevent execution failures. Inspect provenance attributes with xattr, verify the binary with spctl, and follow post-fix checklists to ensure the launchd service runs without Gatekeeper interference.

What's the best way to troubleshoot incorrect user-domain bootstrapping for launchd services?

The best way to troubleshoot incorrect user-domain bootstrapping is to verify the service domain using launchctl and plutil. Distinguish between system and GUI user domains, inspect bootstrap I/O errors with the log command, and apply the correct domain configuration for your daemon.

How do I verify a launchd deployment fix for Go binaries on macOS 12 and later?

Verify a launchd deployment fix for Go binaries on macOS 12 and later by running live checks with spctl, xattr, ps, launchctl, log, and plutil. Confirm the service domain, throttle state, and extended attributes are correct before applying final installation or service-management changes.