cortex-register-taskslisted

Register a Cortex project's five scheduled-task bundles with the Claude Desktop app, from inside a Claude Desktop session, using the app's own scheduled-tasks tools. Use when the user says "register the cortex scheduled tasks", "run cortex-register-tasks", "set up the cortex loops in the app", "activate the cortex tasks", or after `cortex init` / `cortex tasks verify` reports tasks not yet registered. Reads the authoritative plan from `cortex tasks plan --json`, diffs it against mcp__scheduled-tasks__list_scheduled_tasks, creates/updates only this project's tasks (replacing its own superseded legacy tasks), and confirms with `cortex tasks verify`.
pedropacheco95/cortex · ★ 1 · Data & Documents · score 74

Install: claude install-skill pedropacheco95/cortex

# cortex-register-tasks You register this project's five Cortex scheduled-task bundles with the Claude Desktop app the sanctioned way: through the app's own internal MCP tools, from inside a Desktop-spawned session. You never write the app's `scheduled-tasks.json` yourself, and you never touch tasks that belong to another project. ## 0. Preflight — this MUST be a Claude Desktop session The `mcp__scheduled-tasks__*` tools (`create_scheduled_task`, `update_scheduled_task`, `list_scheduled_tasks`, and a delete/remove tool if the app exposes one) are an internal MCP server the Desktop app exposes ONLY to sessions it spawns. Check that they are available to you. **If they are not available: stop.** Do not fall back to editing any file. Tell the user: "This skill needs the Desktop app's own scheduled-tasks tools, which exist only in Claude Desktop sessions. Open this repository in the Claude Desktop app (new session) and say `run cortex-register-tasks` there." Why file-editing is forbidden here: the app loads `scheduled-tasks.json` into memory once per launch and rewrites the whole file from memory on every task event — an external edit is clobbered while the app runs, and a single malformed field makes the app treat the entire file as empty and wipe ALL tasks on its next flush. **Warn the user before you start creating.** The app demands a live approval for every `create_scheduled_task` call and does NOT offer "always allow" for task creation. Tell the user up front: "The ap