What do I need to use Schedule Recipe?

What should run; Cadence and timezone; Where it can run; Where the output should land.

How do I know the Schedule Recipe output is good?

The skill verifies itself against its own quality checks: The cron expression / schedule matches the stated cadence *and timezone* — show the conversion; The setup block is genuinely copy-paste: no ` ` left except secrets, which are named; The run prompt names explicit sources and an output destination; A failed run is visible somewhere a human already looks.

Is Schedule Recipe free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Schedule Recipe

🔵 Stable🕐 updated 2026-07-01 🔷 SkillSpec L3 pm-autopilot

Turn 'run this every Friday at 4pm' into a working, copy-paste schedule on the user's actual runner. Use when asked to schedule a recurring AI task, set up a routine or cron job for a skill, automate a weekly report, or wire a skill into n8n or GitHub Actions. Produces the exact setup for the chosen runner plus the prompt to run, failure alerting, and a first-run test plan.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸What should run — which skill or task, and what inputs it reads each cycle

▸Cadence and timezone — "every Friday 4pm" means nothing without one

▸Where it can run — Claude Code (routines/loops), a server with cron, n8n, or GitHub Actions

▸Where the output should land — file in a repo, Slack/email, a Brain folder, a PR

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓The cron expression / schedule matches the stated cadence *and timezone* — show the conversion

✓The setup block is genuinely copy-paste: no `<placeholders>` left except secrets, which are named

✓The run prompt names explicit sources and an output destination

✓A failed run is visible somewhere a human already looks

✓The recipe includes a manual first-run test, not just "it'll fire Monday"

⚠️ What it refuses to do

Do not pick a runner the user doesn't have — a perfect n8n flow is useless without n8n

Do not write a run prompt that says "as usual" or relies on the agent remembering prior runs without a stored previous edition

Do not schedule without failure alerting — silence and success must not look identical

Do not default to hourly/daily to "be safe" — match the cadence to how often the inputs change

Do not put secrets inline in the setup block — reference the runner's secret store

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="schedule-recipe"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Schedule Recipe is one of 599 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog