[BUG] /schedule skill claims to manage cloud routines, but its MCP only writes local scheduled-tasks (and there is no CLI tool for cloud routines)

Preflight Checklist

• [x] I have searched existing issues
• [x] This is a single bug report
• [x] I am using a current version of Claude Code

Summary

There are (at least) two \"routines\" systems in the Claude ecosystem:

1. Local scheduled-tasks — managed by the bundled mcp__scheduled-tasks__* tools, stored under ~/.claude/scheduled-tasks/<task>/SKILL.md and fired by the local Claude Code daemon.
2. Cloud routines (CCR) — server-side scheduled agents, paired with remote connectors at claude.ai/customize/connectors, referenced from claude.ai/code/routines/{ID}.

From CLI Claude Code, the model has tools for system #1 but no tools at all for system #2. That alone would be acceptable, but the /schedule skill is surfaced to the model with this description:

Create, update, list, or run scheduled remote agents (routines) that execute on a cron schedule.

…while the on-disk SKILL.md and the only tool it can call (mcp__scheduled-tasks__create_scheduled_task) operate exclusively on local files. The two descriptions disagree, and the more visible one is wrong.

What goes wrong in practice

A user with cloud routines asks the CLI \"can you schedule a routine for me?\" or \"list my routines.\" The model:

1. Sees the skill description that says it manages \"remote agents (routines).\"
2. Confidently answers yes.
3. Calls mcp__scheduled-tasks__list_scheduled_tasks → returns No scheduled tasks found.
4. Reports \"you have zero routines\" to a user who can plainly see two in their Routines panel.

Or, on the create path, the model writes a local SKILL.md that the user will never see in their cloud-routines view, then says \"done.\" This has happened to me across multiple sessions; I now have to set up routines manually because the CLI lies about being able to.

Expected behavior

Either:

• (A) Add CLI tools that talk to the cloud-routines API: list_cloud_routines, create_cloud_routine, update_cloud_routine, delete_cloud_routine. Then the /schedule skill description matches reality.
• (B) Tighten the /schedule skill description to explicitly say \"local-only scheduled tasks; cloud routines must be managed at claude.ai\" and provide a deep link. (Per #57864, that deep link is currently 404, which compounds the problem.)

Repro

1. In claude.ai (desktop / web), create a cloud routine. Confirm it appears in your Routines panel.
2. Launch Claude Code CLI.
3. Ask \"list my routines\" or invoke /schedule and pick the list option.
4. Observe: the model returns \"no routines\" or creates a local task that does not appear alongside your cloud routines.

Related (not duplicates)

• #54668 — local scheduled-tasks no longer appear in the Routines panel after 2.1.80 (regression)
• #57864 — claude.ai/code/routines URL referenced by /schedule 404s
• #58130 — /mcp reconnect doesn't refresh remote connectors used by cloud routines

This issue is about the CLI ↔ cloud-routines tooling gap and the skill-description mismatch that fools the model into making confident-but-wrong claims.

Environment

• Claude Code: 2.1.89
• OS: macOS (Darwin 25.0.0)