Agent skill · daymade
macos-watchdog
Designs and audits macOS launchd watchdogs: LaunchAgent/LaunchDaemon setup, plist edits, scheduled self-healing, repeated notifications, apps reopening after quit, crash/repair loops, Script Editor alerts, stop/disable/restart, cooldown/backoff, notification throttling, alert decisions, schedule readback, WatchPaths/FSEvents event triggers. Supports periodic observers. launchd 守护进程、常驻任务、开机自启、后台监控、定时自愈、通知来源排查、事件驱动监控。
What it needs
About 11k tokens when loaded.
What this skill does
macOS Watchdog Bind the ordinary entry before choosing a mechanism Before selecting event/periodic triggers, a transport, or a helper, record these constraints from the original request in the current task plan; do not create a separate document for a simple task: Ordinary entry: where the user will actually start or use the work. When its launcher adopts only some invocation or lifecycle forms, derive the relevant forms from the current launcher and actual requested use; record adopted, bypassed and unverified forms separately, and accept each claimed form through its real consumer. Manual activation: whether the request permits any extra command or setup after delivery. Lifecycle: whether the result covers a session, login, or machine, and which owned components must start and stop with it. If the request explicitly limits the work to a manually run helper, an opt-in experiment, or a read-only design, preserve that scope. Otherwise, accept through the ordinary entry without unrequested manual activation. Reuse the existing session owner for session-bound components; use launchd for login/machine persistence rather than turning every automation request into a global watcher. A completed business round inside a helper alone is component-only evidence: leave the requested result unmet and continue authorized integration. Keep unauthorized or unobserved old-session takeover and other lifecycle coverage unknown; do not stop other tasks or bypass a host refusal to obtain acceptance. When a safety condition is temporary and automatic work must resume afterward, exercise its release in the same running instance: first verify no prohibited action, then remove that condition and require the next eligible event to complete the business action. A separate fresh-instance success, no-action result or health flag does not establish this transition; preserve explicit stop, lost identity and uncertain-delivery boundaries. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills daymade/macos-watchdog