Menu
Suggests relevant cron routines based on user context, goals, and observed patterns
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when adding or reviewing tests for Reborn behavior — choosing a test tier, covering a bug fix, testing model/tool-choice behavior, touching tests/integration or tests/fixtures/llm_traces, or when a test needs Postgres, Docker, or a live LLM.
Navigate building a user-facing feature in the Reborn stack (a capability that crosses product_workflow → composition → webui_v2 → runtime/serve → frontend). Use when planning or implementing any new Reborn settings page, endpoint, facade method, or runtime-backed capability — especially before writing code, to avoid rebuilding what already exists and to wire it in one pass instead of layer-by-layer.
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.
Generate or update the IronClaw architecture overview video using Remotion. Use when asked to update, regenerate, or modify the architecture video, add/remove scenes, or reflect codebase changes in the video.
Use when writing or reviewing a change in crates/ that adds a trait, a crate, a dependency edge, a re-export, or code in ironclaw_reborn_composition — or when deciding whether an abstraction, layer, or crate boundary is justified in the IronClaw Reborn stack.
Use when starting work in the IronClaw repo, deciding where a feature/fix/prompt/doc belongs, tracing how a request flows, looking up which crate owns a subsystem, or when repo docs, the knowledge graph, or component names seem stale, missing, or contradictory.
| name | routine-advisor |
| version | 0.1.0 |
| description | Suggests relevant cron routines based on user context, goals, and observed patterns |
| activation | {"keywords":["every day","every morning","every week","routine","automate","remind me","check daily","monitor","recurring","schedule","habit","workflow","keep forgetting","always have to","repetitive","notifications","digest","review daily","weekly review"],"patterns":["I (always|usually|often|regularly) (check|do|look at|review)","every (morning|evening|week|day|monday|friday)","I (wish|want) (I|it) (could|would) (automatically|auto)","is there a way to (auto|schedule|set up)","can you (check|monitor|watch|track).*for me","I keep (forgetting|missing|having to)"],"tags":["automation","scheduling","personal-assistant","productivity"],"max_context_tokens":1500} |
When the conversation suggests the user has a repeatable task or could benefit from automation, consider suggesting a routine.
Suggest a routine when you notice:
Do not suggest or create a routine when the user asks for a one-time answer or says to do something now, right now, immediately, or ASAP without also asking for scheduling or recurrence.
Be specific and concrete. Not "Want me to set up a routine?" but rather: "I noticed you review PRs every morning. Want me to create a daily 9am routine that checks your open PRs and sends you a summary?"
Always include:
Wait for the user to confirm before creating.
Use the routine_create tool. Before creating, check routine_list to avoid duplicates.
Parameters:
trigger_type: Usually "cron" for scheduled tasksschedule: Standard cron format. Common schedules:
0 9 * * *0 9 * * MON-FRI0 9 * * MON0 9-17/2 * * MON-FRI0 18 * * SUNaction_type: "lightweight" for simple checks, "full_job" for multi-step tasksprompt: Clear, specific instruction for what the routine should docontext_paths: Workspace files to load as context (e.g., ["context/profile.json", "MEMORY.md"])Developer:
Professional:
Health/Personal:
General:
context/profile.json, suggest a Monday routine that reads the profile via memory_read, searches recent conversations for new patterns with memory_search, and updates the profile via memory_write if any fields should change with confidence > 0.6 — be conservative, only update with clear evidence)Before suggesting, consider what tools and extensions are currently available. Only suggest routines the agent can actually execute. If a routine would need a tool that isn't installed, mention that too: "If you connect your calendar, I could also send you a morning briefing with today's meetings."