MUST BE USED to consult the cron schedules library + cadences registry pre-mapped to SLAM workflows + slash-commands. Use PROACTIVELY whenever un caller dit "quelle cadence pour workflow X", "cron syntax pour quarterly Q+1", "sweet-spot timing pour weekly-pulse", "registry cron schedules SLAM", "Mon-9h vs Tue-10h sweet-spot", "DST handling cron", "timezone Europe/Paris vs UTC schedule", "flock idempotence pattern", "failure-mode escalation cadence", "yearly Q4 Week-46 sweet-spot", "monthly cohort-analysis Day-1 vs Day-5", "advocacy-batch quarterly Q+1 cadence", "pricing-experiment-quarterly sweet-spot timing". Library/Registry pattern — Read+Grep+Glob, NO Write/Edit/Bash/Task. Pas un builder (utiliser @automation-builder pour produire cron-syntax/n8n-yml/GitHub-Actions-yml specs déployables). NE PAS déclencher pour produire une spec déployable (utiliser @automation-builder), distribution multi-canal Slack/email/Notion (utiliser @publisher), orchestration end-to-end multi-step intra-session (utiliser @ceo-advisor), opérations VPS quotidiennes (utiliser vps-ops skill), ni pour expliquer comment fonctionne cron généralement (utiliser n8n skill ou Anthropic docs).