Skill

schedule

Create a scheduled task that can be run on demand or automatically on an interval.

Install

Run in your terminal

npx claudepluginhub nickloveinvesting/nick-love-plugins --plugin automation-tools

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

agent-harness-construction

Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.

ecc

140.7k

agent-payment-x402

Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.

ecc

140.7k

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

ecc

140.7k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 20, 2026

Actions

View Source View Plugin View on GitHub View README

2. Draft a prompt

The prompt will be used for future autonomous runs — it must be entirely self-contained. Future runs will NOT have access to this session, so never reference "the current conversation," "the above," or any ephemeral context.

Include in the description:

A clear objective statement (what to accomplish)

Specific steps to execute

Any relevant file paths, URLs, repositories, or tool names

Expected output or success criteria

Any constraints or preferences the user expressed

Write the description in second-person imperative ("Check the inbox…", "Run the test suite…"). Keep it concise but complete enough that another Claude session could execute it cold.

4. Determine scheduling

Pick one:

Recurring ("every morning", "weekdays at 5pm", "hourly") → cronExpression

One-time with a specific moment ("remind me in 5 minutes", "tomorrow at 3pm", "next Friday") → fireAt ISO timestamp

Ad-hoc (no automatic run; user will trigger manually) → omit both

Ambiguous → propose a schedule and ask the user to confirm before proceeding

cronExpression: Evaluated in the user's LOCAL timezone, not UTC. Use local times directly — e.g. "8am every Friday" → 0 8 * * 5.

fireAt: Compute the exact moment and emit a full ISO 8601 string with timezone offset, e.g. 2026-03-05T14:30:00-08:00. Never use cron for one-time tasks — cron has no one-shot semantics.

Finally, call the "create_scheduled_task" tool.

You are creating a reusable shortcut from the current session. Follow these steps:

1. Analyze the session

Review the session history to identify the core task the user performed or requested. Distill it into a single, repeatable objective.

2. Draft a prompt

Include in the description:

A clear objective statement (what to accomplish)
Specific steps to execute
Any relevant file paths, URLs, repositories, or tool names
Expected output or success criteria
Any constraints or preferences the user expressed

Write the description in second-person imperative ("Check the inbox…", "Run the test suite…"). Keep it concise but complete enough that another Claude session could execute it cold.

3. Choose a taskName

Pick a short, descriptive name in kebab-case (e.g. "daily-inbox-summary", "weekly-dep-audit", "format-pr-description").

4. Determine scheduling

Pick one:

Recurring ("every morning", "weekdays at 5pm", "hourly") → cronExpression
One-time with a specific moment ("remind me in 5 minutes", "tomorrow at 3pm", "next Friday") → fireAt ISO timestamp
Ad-hoc (no automatic run; user will trigger manually) → omit both
Ambiguous → propose a schedule and ask the user to confirm before proceeding

cronExpression: Evaluated in the user's LOCAL timezone, not UTC. Use local times directly — e.g. "8am every Friday" → 0 8 * * 5.

fireAt: Compute the exact moment and emit a full ISO 8601 string with timezone offset, e.g. 2026-03-05T14:30:00-08:00. Never use cron for one-time tasks — cron has no one-shot semantics.

Finally, call the "create_scheduled_task" tool.