/loop commands not discoverable when checking for running loops

Problem

When a user asks "do we have any /loop commands still running?", Claude checks TaskList (which returns empty) and reports no loops are running — even when a /loop cron job is actively firing every 10 minutes.

The /loop skill creates entries via CronCreate, but there's no indication in the skill description or system behavior that running loops should be checked with CronList/CronDelete rather than TaskList.

Impact

A missed running loop kept firing a costly prompt every 10 minutes until the user noticed and asked again. Significant token waste.

Expected behavior

When asked about running /loop commands, Claude should check CronList (not TaskList). Either:

1. The /loop skill description should mention that loops are cron jobs (checked via CronList), or
2. Asking about "loops" should automatically route to CronList, or
3. TaskList should surface cron entries (or at least mention they exist separately)

Steps to reproduce

1. Run /loop 10m <some prompt>
2. Ask "Do we have any /loop commands still running? Please stop them."
3. Claude checks TaskList, finds nothing, reports no loops running
4. The loop continues firing in the background