Agent skill

Schedule Recipe

by mohitagw15856 in mohitagw15856/pm-claude-skills

Turn 'run this every Friday at 4pm' into a working, copy-paste schedule on the user's actual runner.

MITAuto-check passedProductivity & Automation

Install Schedule Recipe

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill schedule-recipe -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills schedule-recipe --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/schedule-recipe .claude/skills/schedule-recipe && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
schedule-recipe
GitHub stars
1.4k
Token cost
~1.1k tokens
SKILL.md length
606 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Turn 'run this every Friday at 4pm' into a working, copy-paste schedule on the user's actual runner.

  • Works in 5 steps: The skill to load and the artifact to… → The sources to read this cycle —… → Where to write the result and how to… → …
  • Asked to schedule a recurring AI task
  • SKILL.md covers What This Skill Produces, Required Inputs, Runner Selection and The Run Prompt, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Schedule Recipe is an agent skill from mohitagw15856/pm-claude-skills. 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.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Scheduled and recurring tasks, Workflow automation and CI/CD. It works with GitHub Actions and n8n. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked to schedule a recurring AI task
  • Set up a routine
  • Cron job for a skill
  • Automate a weekly report

Example prompts

  • “run this every Friday at 4pm”
  • “/schedule-recipe”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. The skill to load and the artifact to produce
  2. The sources to read this cycle — explicit paths/URLs, not "the usual"
  3. Where to write the result and how to mark the edition (date, sources read)
  4. What to do on missing sources — name the failure behaviour, never fabricate
  5. Delta instruction if recurring: read the previous edition first and report changes (see delta-briefing)

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Schedule Recipe loads about 1.1k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 606 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~98
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 606 words, ~1,135 tokens.

Download SKILL.mdSave it as .claude/skills/schedule-recipe/SKILL.md (or your agent's skills folder).
name
schedule-recipe
description
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.

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:

RunnerChoose whenSetup shape
Claude Code routine (/schedule)The user lives in Claude Code and the task needs an agent (reads repos, runs skills)A scheduled cloud agent with the run prompt
Claude Code /loopSame-session polling or short-lived recurrence, not a standing schedule/loop <interval> <command>
GitHub Actions cronInputs and output both live in a repo; team wants runs versioned and reviewableA workflow YAML with schedule: trigger
n8n / MakeThe trigger or output is a SaaS app (Slack, CRM, sheets)A workflow calling the skills REST API
System cronA server exists and the task is a scriptA crontab line invoking the CLI

State the choice and the runner-up. If the user names a runner, use it — don't relitigate.

The Run Prompt

Every recipe includes the prompt the scheduled run executes. It must contain:

  1. The skill to load and the artifact to produce
  2. The sources to read this cycle — explicit paths/URLs, not "the usual"
  3. Where to write the result and how to mark the edition (date, sources read)
  4. What to do on missing sources — name the failure behaviour, never fabricate
  5. Delta instruction if recurring: read the previous edition first and report changes (see delta-briefing)
Show full SKILL.md (243 more words)Show less

Output Format

Schedule Recipe: [task] — [cadence]

Runner: [choice] — because [one line]. Runner-up: [alternative] if [condition].

Setup (copy-paste):

[the exact command / crontab line / workflow YAML / n8n outline]

Run prompt:

[the full prompt the scheduled agent executes each cycle]

Failure alerting: [how a failed/skipped run becomes visible — e.g. the run posts an error note to the same channel it would post the brief].

First-run test: trigger one run manually now; check [the two or three things that prove it worked] before trusting the schedule.

Quality Checks

  • 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"

Anti-Patterns

  • 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

Example Trigger Phrases

  • "Schedule a recurring AI task."
  • "Set up a routine."
  • "Automate a weekly report."
  • "Wire a skill into n8n or GitHub Actions."

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/schedule-recipe of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Schedule Recipe next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Schedule Recipe compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Schedule Recipe this skillmohitagw15856/pm-claude-skills1.4k—~1.1kAutomated safety check: PassMIT
N8n Workflowsvibeeval/vibecosystem532—~3.3kAutomated safety check: PassMIT
Deploy Release Testvercel/next.js143k—~1.2kAutomated safety check: PassMIT
GitHub Actions CreatorFNOSP/FlyNarwhal5091 repos~2.4kAutomated safety check: PassAGPL-3.0
Aeon Agent Setup and Managementaeonfun/aeon770—~9kAutomated safety check: WarnMIT
Running GitHub Actions Efficientlykajisho5/ffmpeg-skill1.9k—~3.3kAutomated safety check: NotesMIT

Similar skills

  • N8n Workflows

    vibeeval/vibecosystem

    n8n otomasyon workflow'lari. An agent skill from vibeeval/vibecosystem.

    532 GitHub stars~3.3k tokensUpdated 2 mo ago
    Productivity & AutomationAuto-check passed
  • Deploy Release Test

    vercel/next.js

    Official

    Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the teste2edeployrelease.yml GitHub Actions workflow.

    143k GitHub stars~1.2k tokensUpdated today
    DevOps & CloudAuto-check passed
  • GitHub Actions Creator

    FNOSP/FlyNarwhal

    A skill your agent uses when the user wants to create, generate, or set up a GitHub Actions workflow.

    509 GitHub starsUsed in 1 repo~2.4k tokens
    DevOps & CloudAuto-check passed
  • Sets up and manages an Aeon agent instance that runs skills on a schedule through GitHub Actions: starting, rescheduling, debugging, editing skills and mining chat history.

    770 GitHub stars~9k tokensUpdated yesterday
    Productivity & AutomationAuto-check: warnings
  • Cut GitHub Actions minutes and wall-clock time without losing coverage — the OS billing multiplier (macOS 10x / Windows 2x / Linux 1x), trigger hygiene that stops push+pullrequest double-firing…

    1.9k GitHub stars~3.3k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • Dokan Run Test Suite

    getdokan/dokan

    Execute the Dokan Playwright test suite (E2E + API), locally or via GitHub Actions.

    288 GitHub stars~4.7k tokensUpdated 2 days ago
    Testing & QAAuto-check: notes

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed

Questions about Schedule Recipe

What does Schedule Recipe do?

Turn 'run this every Friday at 4pm' into a working, copy-paste schedule on the user's actual runner. Schedule Recipe is an agent skill from mohitagw15856/pm-claude-skills. Turn 'run this every Friday at 4pm' into a working, copy-paste schedule on the user's actual runner.

When should I use Schedule Recipe?

Schedule Recipe fits situations like: asked to schedule a recurring AI task; set up a routine; cron job for a skill; automate a weekly report.

How do I install Schedule Recipe in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill schedule-recipe -a claude-code`. Or copy the skill folder (skills/schedule-recipe in mohitagw15856/pm-claude-skills) into .claude/skills/schedule-recipe in your project. Claude Code loads it when a task matches its description.

How do I install Schedule Recipe in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill schedule-recipe -a codex`. Or copy the skill folder (skills/schedule-recipe in mohitagw15856/pm-claude-skills) into .agents/skills/schedule-recipe in your project. Codex loads it when a task matches its description.

Can I use Schedule Recipe in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill schedule-recipe -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/schedule-recipe, .gemini/skills/schedule-recipe, .github/skills/schedule-recipe and .opencode/skills/schedule-recipe in your project.

What does Schedule Recipe need to run?

SKILL.md names no scripts, command-line tools or credentials: Schedule Recipe is instructions for the agent only.

Does Schedule Recipe access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Schedule Recipe safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Schedule Recipe use?

Schedule Recipe is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Schedule Recipe use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Schedule Recipe?

Skills that share tags, products or a category with Schedule Recipe: N8n Workflows (vibeeval/vibecosystem, 532 stars), Deploy Release Test (vercel/next.js, 143k stars), GitHub Actions Creator (FNOSP/FlyNarwhal, 509 stars) and Aeon Agent Setup and Management (aeonfun/aeon, 770 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Schedule Recipe?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.