schedule

Name: schedule
Author: thtskaran

16stars2forks

How to install schedule?

thtskaran/claude-skills/schedule

$npx -y skills add thtskaran/claude-skills --skill schedule

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	You are creating a reusable shortcut from the current session. Follow these steps:
2
3	## 1. Analyze the session
4
5	Review the session history to identify the core task the user performed or requested. Distill it into a single, repeatable objective.
6
7	## 2. Draft a prompt
8
9	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.
10
11	Include in the description:
12	- A clear objective statement (what to accomplish)
13	- Specific steps to execute
14	- Any relevant file paths, URLs, repositories, or tool names
15	- Expected output or success criteria
16	- Any constraints or preferences the user expressed
17
18	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.
19
20	## 3. Choose a taskName
21
22	Pick a short, descriptive name in kebab-case (e.g. "daily-inbox-summary", "weekly-dep-audit", "format-pr-description").
23
24	## 4. Determine scheduling
25
26	Pick one:
27	- Recurring ("every morning", "weekdays at 5pm", "hourly") → `cronExpression`
28	- One-time with a specific moment ("remind me in 5 minutes", "tomorrow at 3pm", "next Friday") → `fireAt` ISO timestamp
29	- Ad-hoc (no automatic run; user will trigger manually) → omit both
30	- Ambiguous → propose a schedule and ask the user to confirm before proceeding
31
32	cronExpression: Evaluated in the user's LOCAL timezone, not UTC. Use local times directly — e.g. "8am every Friday" → `0 8 * * 5`.
33
34	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.
35
36	Finally, call the "create_scheduled_task" tool.

People who liked this also viewed

6 picks

Type

requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsSkillsJul 2026176k259k
code-reviewSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026158k181k
receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performativeSkillsJul 2026146k259k
baoyu-format-markdownFormats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or imprSkillsJul 202625k24k
code-review-excellenceMaster effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing reSkillsJul 202625k38k
code-review-and-qualityConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensiSkillsJul 202618k80k

schedule

16stars2forks

View on GitHub

How to install schedule?

thtskaran/claude-skills/schedule

$npx -y skills add thtskaran/claude-skills --skill schedule

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	You are creating a reusable shortcut from the current session. Follow these steps:
2
3	## 1. Analyze the session
4
5	Review the session history to identify the core task the user performed or requested. Distill it into a single, repeatable objective.
6
7	## 2. Draft a prompt
8
9	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.
10
11	Include in the description:
12	- A clear objective statement (what to accomplish)
13	- Specific steps to execute
14	- Any relevant file paths, URLs, repositories, or tool names
15	- Expected output or success criteria
16	- Any constraints or preferences the user expressed
17
18	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.
19
20	## 3. Choose a taskName
21
22	Pick a short, descriptive name in kebab-case (e.g. "daily-inbox-summary", "weekly-dep-audit", "format-pr-description").
23
24	## 4. Determine scheduling
25
26	Pick one:
27	- Recurring ("every morning", "weekdays at 5pm", "hourly") → `cronExpression`
28	- One-time with a specific moment ("remind me in 5 minutes", "tomorrow at 3pm", "next Friday") → `fireAt` ISO timestamp
29	- Ad-hoc (no automatic run; user will trigger manually) → omit both
30	- Ambiguous → propose a schedule and ask the user to confirm before proceeding
31
32	cronExpression: Evaluated in the user's LOCAL timezone, not UTC. Use local times directly — e.g. "8am every Friday" → `0 8 * * 5`.
33
34	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.
35
36	Finally, call the "create_scheduled_task" tool.

People who liked this also viewed

6 picks

Type