schedule-remove

To safely unschedule a skill, the tool presents your current schedule entries from onebrain.yml, asks you to confirm which entry to delete, and rewrites the configuration file atomically to remove it.

Yes, removing a schedule entry also unregisters the corresponding launchd job. After deleting the entry from onebrain.yml, the skill invokes a schedule register refresh to delete the associated launchd plist.

If no schedules exist in onebrain.yml, the skill clearly reports the empty state and halts the process, preventing you from attempting to delete non-existent cron schedule entries or modifying launchd jobs unnecessarily.

No, you do not need to manually edit configuration files to stop an automatic skill invocation. The skill handles reading and rewriting onebrain.yml atomically while managing the launchd job unregistration automatically.

The best way to stop recurring daily tasks managed by launchd and cron is to use a guided removal skill that confirms your intent before deleting the schedule entry and refreshing the launchd registration.

If updating onebrain.yml or refreshing launchd fails during schedule removal, the skill surfaces the specific errors encountered, allowing you to diagnose the configuration or launchd job failure.