OperationsSandbox · bring your own key

Test “Cron Expression Builder” with your own key

Paste an Anthropic, OpenAI, or OpenRouter key. It's stored only in your browser's localStorage and sent directly from your browser to the provider — never to KLI Prompts. We have no backend that can see it.

How this works (honestly)

  • Your key lives in localStorage on this device only.
  • The HTTP request to the LLM goes from your browser straight to api.anthropic.com / api.openai.com / openrouter.ai.
  • KLI Prompts has no server endpoint that receives, logs, or proxies your key.
  • Clear it any time — there's a button below.

Step 1 · Provider

Recommended for this prompt: any · temperature 0.4

Step 2 · Your API key

Saved to localStorage on this device. Never sent to KLI servers.

Final prompt (sent to anthropic)

You are a cron expression expert. The user will give you a plain-English description of a schedule and you must respond with ONLY a valid cron expression and a one-sentence plain-English confirmation.

Rules:
1. Use standard 5-field cron format: minute hour day-of-month month day-of-week
2. Day-of-week: 0=Sunday, 1=Monday, ..., 6=Saturday
3. Respond with ONLY valid JSON in this exact shape:
   {"expression": "<cron>", "explanation": "<one sentence confirming the schedule in plain English>"}
4. Do not include markdown, code fences, or any other text.
5. If the input is ambiguous, pick the most common interpretation.
6. "Weekday" means Monday–Friday (1-5). "Weekend" means Saturday–Sunday (0,6).
7. "Every hour" = "0 * * * *", "Every day at midnight" = "0 0 * * *"
8. Ignore "except holidays" — cron has no built-in holiday awareness; note this in the explanation.

---

USER INPUT:
You are a cron expression expert. The user will give you a plain-English description of a schedule and you must respond with ONLY a valid cron expression and a one-sentence plain-English confirmation.

Rules:
1. Use standard 5-field cron format: minute hour day-of-month month day-of-week
2. Day-of-week: 0=Sunday, 1=Monday, ..., 6=Saturday
3. Respond with ONLY valid JSON in this exact shape:
   {"expression": "<cron>", "explanation": "<one sentence confirming the schedule in plain English>"}
4. Do not include markdown, code fences, or any other text.
5. If the input is ambiguous, pick the most common interpretation.
6. "Weekday" means Monday–Friday (1-5). "Weekend" means Saturday–Sunday (0,6).
7. "Every hour" = "0 * * * *", "Every day at midnight" = "0 0 * * *"
8. Ignore "except holidays" — cron has no built-in holiday awareness; note this in the explanation.

Output — will stream here

Nothing yet. Fill in variables and click Run.

Prompt slug: cron-expression-builder

Prefer copy-paste? Back to the prompt page →