How do I install the Schedule skill?

Run npx skillmds add organvm-iv-taxis/schedule in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Schedule safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Schedule?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Schedule free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Schedule?

organvm-iv-taxis (@organvm-iv-taxis) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Schedule by organvm-iv-taxis — Agent Skill

Name: Schedule
Rating: 4.5 (4 reviews)
Author: organvm-iv-taxis

Schedule

Create a scheduled task that can be run on demand or automatically on an interval. Distills the current session into a self-contained reusable prompt with cronExpression or fireAt, then calls the create_scheduled_task tool. Use when the user wants a recurring or one-time task scheduled — e.g. 'remind me every Friday', 'run this hourly', 'schedule a daily inbox check'.

File contents

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

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.

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.

---name: scheduledescription: Create a scheduled task that can be run on demand or automatically on an interval. Distills the current session into a self-contained reusable prompt with cronExpression or fireAt, then calls the create_scheduled_task tool. Use when the user wants a recurring or one-time task scheduled — e.g. 'remind me every Friday', 'run this hourly', 'schedule a daily inbox check'.license: MIT--- 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 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. ## 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.

Frequently asked questions