メニュー
Schedule recurring work, reminders, and periodic checks through the Aliceloop daemon cron service.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Manage chat threads — create, list, inspect, delete, and search conversations. Use when users want to organize chats or open a specific thread.
当agent因maxIterations中断时，恢复 Task Working Memory 并继续执行未完成的任务。用户说"继续"时自动触发。
Enter a planning-first workflow with structured steps, checkpoints, and explicit approval before execution.
Planned Alice-native selfie workflow for self-portraits, local album management, and future face-reference generation support.
Track durable Task Working Memory across sessions with the local Aliceloop tracked-task CLI.
Extract content from Twitter/X links, x.com links, twitter.com links, and tweet URLs, or use OpenCLI for logged-in Twitter/X actions such as search, profile reads, timeline reads, bookmarks, notifications, and lightweight interactions.
| name | scheduler |
| description | Schedule recurring work, reminders, and periodic checks through the Aliceloop daemon cron service. |
| allowed-tools | ["bash","read","write"] |
Use this skill when the user asks for recurring jobs, reminders, or timed follow-up work.
aliceloop cron list
aliceloop cron add NAME at SCHEDULE --prompt "..."
aliceloop cron remove CRON_ID
# Run every 30 minutes
aliceloop cron add Inbox sweep at "every 30m" --prompt "Review the latest open issues and summarize the blockers."
# Run daily at a local wall-clock time
aliceloop cron add Daily standup at "daily 09:00" --prompt "Summarize what changed since yesterday and what to do next."
# Run weekly on a named weekday
aliceloop cron add Friday review at "weekly fri 16:30" --prompt "Write a short weekly review and identify unfinished work."
# Run once at an absolute time
aliceloop cron add Launch reminder at "2026-03-21T18:00:00-07:00" --prompt "Remind me to verify the release checklist."
aliceloop cron list before creating duplicates.--session SESSION_ID when the scheduled prompt should always land in a specific thread.every 10s is supported for smoke tests and quick verification, but minute/hour/day cadences are usually better for real work.