القائمة
Create and edit cron job definitions in .agent/crons/. Use when the user wants to schedule recurring workflow or prompt runs, adjust cron schedules, or validate cron YAML.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Picking the right built-in channel for outbound communication (SMS, voice, chat, email).
Surface typed UI cards in the console chat via the propose_card tool. Use when the user needs to take a configuration action (set up a channel, configure a webhook, install a skill) or when you want to post a standout notice. Covers when to use a card vs. prose, which kind to pick, and how the tool blocks until the user decides.
Edit the runtime setup via get_setup and patch_setup. Use when the user asks to change the agent model, edge model profiles, agent definitions, or channel display metadata. Covers what is editable, what is operator-only, and the JSON-Pointer patch format.
Create executable agent workflows in .agent/workflows/. Use when the user wants to define, scaffold, validate, or edit a multi-step workflow pipeline that uses tools, delegate steps, approval gates, or parallel branches.
| name | cron-jobs |
| description | Create and edit cron job definitions in .agent/crons/. Use when the user wants to schedule recurring workflow or prompt runs, adjust cron schedules, or validate cron YAML. |
Create and edit cron job definitions in .agent/crons/*.yaml.
name: my-cron
description: What it does
schedule: "0 9 * * 1-5"
timezone: America/Los_Angeles
enabled: true
type: workflow
# For type: workflow
workflow: my-workflow
inputs:
key: value
# For type: prompt
prompt: "Do the thing"
agent: main
# Optional delivery routing
slack_channel: "#channel"
python3 {baseDir}/scripts/init_cron.py <name> to scaffold a new YAML file in .agent/crons/.python3 {baseDir}/scripts/validate_cron.py <name-or-path> to validate the definition.For guidance on choosing between workflow and prompt jobs, read cron-types.md.
┌───────── minute (0-59)
│ ┌─────── hour (0-23)
│ │ ┌───── day of month (1-31)
│ │ │ ┌─── month (1-12)
│ │ │ │ ┌─ day of week (0-6, Sun=0)
│ │ │ │ │
* * * * *
Common patterns:
0 9 * * 1-5 for weekdays at 9am*/30 * * * * for every 30 minutes0 0 * * * for daily at midnight0 9 * * 1 for every Monday at 9am0 */6 * * * for every 6 hoursEdit the YAML file directly at .agent/crons/<name>.yaml. After editing, run the validator again.
Use slack_channel when every run should post a summary.
slack_channel: "#team-updates"
For polling or monitoring jobs that often have nothing to report, omit slack_channel and have the prompt post to Slack only when there is something worth sending.
type: prompt
prompt: |
Check for new items and process them.
If you handled something, post a short summary to Slack.
If there is nothing new, finish silently.
.agent/crons/ and use .yamlname must match the filenametype: workflow requires workflowtype: prompt requires promptenabled: false to disable a cron without deleting it.agent/workflows/