Agent skill · Testing & QA

schedule-recipe

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.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill schedule-recipe --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/schedule-recipe/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Schedule Recipe Skill Convert a recurring intent — "competitive briefing every Monday 8am" — into the concrete, copy-paste setup for whatever runner the user actually has, with failure handling so it degrades loudly, not silently. ## What This Skill Produces - A **runner recommendation** (or confirmation of the user's choice) with the reason - The **exact setup** — command, cron expression, or workflow file — ready to paste - The **run prompt**: what the scheduled agent should do each cycle, including which skill to load - **Failure alerting and a first-run test plan** ## Required Inputs Ask for (if not already provided): - **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 ## Runner Selection Pick the simplest runner the user already has, in this order: | Runner | Choose when | Setup shape | |---|---|---| | **Claude Code routine** (`/schedule`) | The user lives in Claude Code and the task needs an

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Runner Selection
  4. The Run Prompt
  5. Output Format
  6. Schedule Recipe: [task] — [cadence]
  7. Quality Checks
  8. Anti-Patterns
More from pm-claude-skills
All skills →
About this skill
What does the schedule-recipe skill do?

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.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill schedule-recipe --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going