/schedule fails to connect to remote backend; retries return ambiguous non-error/non-success responses

Environment: Claude Code CLI, Windows 11, session using Sonnet 5 (claude-sonnet-5)

What I did:
Tried to create a one-time scheduled reminder via the /schedule skill (and had Claude invoke it directly too), e.g.:
"Create a one-time scheduled reminder for [date] to revisit [topic]."

What happened:

1. First attempt (both via Claude invoking the skill, and via me running /schedule directly): explicit error —

"We're having trouble connecting with your remote claude.ai account to set up a scheduled task. Please try /schedule again in a few minutes."

1. Three subsequent retries (a few minutes apart): no error this time, but also no confirmation of success — the skill just returned "Skill /schedule is already loaded above; instructions unchanged" with no indication whether a job was actually created.

Expected: Either a clear success confirmation (job ID, scheduled time, etc.) or a clear, consistent error — not a silent/ambiguous middle state where it's impossible to tell if a scheduled task exists or not.

Impact: Can't tell whether any scheduled tasks were actually created from these attempts (risk of either zero reminders, or duplicate/orphaned ones I can't see or manage). No fallback available — Claude's session-local cron tool (CronCreate) isn't usable as a substitute since it's explicitly non-durable and dies when the session ends, which doesn't help for a reminder weeks out.

Ask:

• Fix the backend connectivity issue for /schedule.
• Make failure/success state unambiguous on every call, not just the first.