Loading...
Loading...
Found 50 Skills
Trigger: Invoked when multiple tasks are competing for time, attention, computing power or budget at the same time, and it is necessary to determine the main attack direction and stop dispersing efforts; common signals include too many priorities, tight resources, scattered progress, and the need to decide what to do first. English: Trigger when limited resources are being split across too many tasks and one main target must be chosen. Use this skill to concentrate effort, sequence work decisively, and finish a meaningful breakthrough before expanding.
Schedule and manage cron jobs. Use when: user needs to create, list, remove, or test scheduled tasks.
Guide for Convex actions, scheduling, cron jobs, and orchestration patterns. Use when implementing external API calls, background jobs, scheduled tasks, cron jobs, or multi-step workflows. Activates for action implementation, ctx.scheduler usage, crons.ts creation, or long-running workflow tasks.
Use this for designing complex workflows, scheduled jobs, and task orchestration (Airflow, Prefect, Temporal, Cron, Celery).
Triggered automatically at the start of each new top-level conversation to establish the general principle of "seeking truth from facts", and select downstream skills for subsequent tasks only when clearly applicable. Skip this skill if you are a delegated sub-agent performing a single specific task. English: Trigger at the start of each new top-level conversation to establish the core methodology and select downstream skills only when clearly useful. Skip this skill when you are a delegated sub-agent handling a narrow, concrete task.
Used when users want to analyze task scheduling, personnel distribution, man-hours, and risk status under a specific TAPD requirement.
Create an OpenClaw cron job that sends a message to the specified channel after execution. Use this skill when the user mentions phrases like "create scheduled task", "new cron", "set scheduled execution", "run periodically", "scheduled task", "every", "every minute", "every hour", "every week", "every month", or "every X hours between A and B". Collect the task name, task description, and execution time (supports four modes: fixed time, interval loop, periodic time, and scheduled range) through conversation, automatically obtain the session key (no user cooperation required), then construct and execute the openclaw cron add command.
Symptom-based background task troubleshooting - decision trees for 'task never runs', 'task terminates early', 'works in dev not prod', 'handler not called', with time-cost analysis for each diagnosis path
Manage concurrent background workers with scheduling, dependencies, health monitoring, and automatic disabling of failing workers.
Generate headless Claude Code cron jobs from a task description and schedule. Creates a wrapper script with safety mechanisms (lockfile, budget cap, dry-run default, logging) and installs crontab entries via deterministic Python script. Use when user says "schedule", "run every", "cron job", "run twice daily", "run hourly", "run daily", "run weekly", or "schedule task".
Django + Celery async task patterns — configuration, task design, beat scheduling, retries, canvas workflows, monitoring, and testing. Use when adding background jobs, scheduled tasks, or async processing to a Django app.
Generates a one-page Monday morning briefing — cash, sales, pipeline, week ahead, top three to-dos. Accepts optional post destination and save-to arguments.