Cron Translator: Explain an Expression

Cron translator for expression explanations

Paste the schedule text from an app to learn what it means in plain language. If you want future times, add the city or region where you want them shown and how many to list.

Use with your AI

For tasks with several steps, continue in the AI you already use.

CodexClaude CodeCursorWindsurfCline

View instructions

Use cron-explain-strale to explain the exact schedule text the user shares. The user should be able to copy it from an app; do not ask them to construct or edit it. If it is missing, ask them to copy the schedule text from where it appears. When the user gives a city or region, map it to a time zone only when unambiguous; ask if the location is unclear. Include a requested number of upcoming times when given; otherwise use the documented default only when it applies and check the actual count returned. Keep any dates and times with the stated time basis. Do not claim the job was installed or ran. Check current availability, price and authorized budget before use.

Task:
I copied this schedule from [an app’s settings]: [0 9 * * 1-5]. Explain in plain language when it runs. If available, show the next [3] times for [Shanghai, China].

Paste into your connected AI's conversation.

Connection guide

The final charge is based on confirmed usage. Unused reserved credits return to your available balance.

Strale

Cron translator for expression explanations

Paste the schedule text from an app to learn what it means in plain language. If you want future times, add the city or region where you want them shown and how many to list.

You receive

Your Agent can organize the actual explanation and any upcoming dates and times into a schedule note, alongside the original expression and requested settings. This helps you compare the interpretation with the scheduler you intend to use.

Start with your task

I copied this schedule from [an app’s settings]: [0 9 * * 1-5]. Explain in plain language when it runs. If available, show the next [3] times for [Shanghai, China].

What to know

The response may leave the cron dialect, reference time or time-zone handling unstated. Upcoming times do not confirm that a job was installed or ran; check the interpretation in the intended scheduler before relying on it.

Inputs & outputs

Inspect the current inputs, availability, and maximum charge before starting.

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
queryParams`queryParams`	`object`	Required	Required fields `cron_expression`
Requested upcoming-time count`queryParams.num_next`	`integer`	Optional	How many upcoming times to request, optionally. The input description states a default of 5, but the schema sets no default or bounds. The actual returned count may differ.
Time zone`queryParams.timezone`	`string`	Optional	Optional time zone for the requested interpretation. No identifier format or default is specified; check the response for the time zone actually used.
Cron expression`queryParams.cron_expression`	`string`	Required	The expression to explain. Its input description refers to 5–7 fields; the accepted dialect and syntax rules are not specified. Preserve the original text.

View raw JSON

{
  "type": "object",
  "required": [
    "queryParams"
  ],
  "properties": {
    "queryParams": {
      "type": "object",
      "required": [
        "cron_expression"
      ],
      "properties": {
        "num_next": {
          "type": "integer",
          "description": "Number of next runs (default 5)"
        },
        "timezone": {
          "type": "string"
        },
        "cron_expression": {
          "type": "string",
          "description": "Cron expression (5-7 fields)"
        }
      }
    }
  },
  "additionalProperties": false
}

Result schema

Output fields have not been documented yet.

Additional notes

Strale’s capability notes describe readable explanations of cron expressions and upcoming execution times. Start with the expression you want to understand; include a time zone and requested count when they matter to your task. Review whichever explanation and times the actual response supplies.

Keep the original expression, requested settings and returned dates or offsets together. A requested count does not establish how many times will be returned. If the dialect, time zone or reference time is unstated, keep that uncertainty visible and compare the interpretation with your intended scheduler.

Cron translator for expression explanations

Cron translator for expression explanations

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Get your AI assistant ready

Copy the schedule text

Choose the time and number