Menu
Remove a scheduled OneBrain skill. Shows the current schedule list and lets the user pick which entry to remove.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Clone your agent's portable context (agent folder including MEMORY.md) to a folder for transfer to another vault. Use only when the user explicitly wants to migrate or copy agent memory to a new vault. Do NOT use for: backing up the whole vault, updating OneBrain (use update), or reviewing memory (use memory-review).
List all available OneBrain commands with descriptions and use cases. Invoke when user asks what you can do, wants to see commands, or seems confused about capabilities. Do NOT use for: actually running a command (identify the right skill and invoke it directly), answering questions about vault content (search directly), or general Claude questions.
Interactive review of all memory/ files — keep, update, deprecate, or delete entries one by one. Use when the user wants to audit and prune accumulated memory — 'review my memory', 'clean up what you remember'. Do NOT use for: teaching a new fact (use learn), recalling something specific (read memory directly), or batch-promoting session insights (use recap).
First-run setup for OneBrain : personalize identity, communication style, and vault configuration. Use only on first install or when the user wants to fully reconfigure OneBrain from scratch — manual only. Do NOT use for: teaching a single preference (use learn), updating system files (use update), or reviewing memory (use memory-review).
Migrate vault structure : either full 5-folder → 8-folder migration, or subfolder organization for flat notes. Use only when the user explicitly wants to restructure the entire vault layout — manual only, high impact. Do NOT use for: moving a single note (do it directly), processing inbox (use consolidate), or routine note organization.
Interactive wizard to add a scheduled OneBrain skill. Walks user through skill selection, frequency, time, and writes to onebrain.yml + invokes onebrain schedule register.
| name | schedule-remove |
| description | Remove a scheduled OneBrain skill. Shows the current schedule list and lets the user pick which entry to remove. |
| schedulable | false |
Safely unschedule a skill: presents the current schedule, confirms intent, removes the entry from onebrain.yml, and unregisters the corresponding launchd job.
Run the /schedule-list logic (read onebrain.yml schedule: block + call onebrain schedule register --status) to display the current entries.
If no entries are found:
No scheduled skills to remove.
→ Run /schedule-add to set one up.
Stop.
Show via AskUserQuestion:
/skill-name with cron and frequency as description
/daily, description: 0 9 * * * — daily at 09:00Store: chosen_entry (the matched onebrain.yml schedule entry).
Show via AskUserQuestion:
{chosen_skill} scheduled at {cron} ({frequency_description})? This stops all automatic invocations."If Cancel, stop.
Read onebrain.yml. Remove the matching entry from the schedule: block.
Write the full updated onebrain.yml back atomically:
onebrain.yml.tmp in the vault root.onebrain.yml.If the write fails, delete onebrain.yml.tmp if it exists and report the error. Do not proceed to Step 5.
Run from the vault root:
onebrain schedule register --refresh
This re-reads onebrain.yml (now without the removed entry) and deletes the corresponding launchd plist.
If the command fails, report the error. onebrain.yml has already been updated — the user can retry onebrain schedule register --refresh manually.
Say:
✓ Removed {chosen_skill} from schedule. The launchd plist has been deleted.
schedule: block in onebrain.yml; this is valid and the block is preserved (not deleted) so future /schedule-add runs can append to it.schedule register --refresh failure — launchd plist may still exist; surface it and suggest manual retry.