schedule 精选
Create or update a scheduled task that runs automatically. Use when the user says things like \"every day\", \"each morning\", \"remind me in an hour\", \"run this at noon\", or wants to reschedule an existing task.
安装方式
cp -r Anthropic/claude-code/skills/anthropic-skills/schedule ~/.claude/skills/schedule把该 skill 目录放进客户端 skills 目录。不同客户端的目录可能不同,Claude Code 默认是 ~/.claude/skills/
https://raw.githubusercontent.com/asgeirtj/system_prompts_leaks/a09e0e708710093ed9fc15fb24bfc1374f584da4/Anthropic/claude-code/skills/anthropic-skills/schedule/SKILL.md下载后另存为 ~/.claude/skills/schedule/SKILL.md。链接锁定采集时的 commit,内容与本站展示一致。
整仓一次性获取:git clone --depth 1 https://github.com/asgeirtj/system_prompts_leaks.git
依赖与权限
- 无需 API Key
- 无需联网
- 无外部命令依赖
- 以上为按正文与 frontmatter 自动推断的信号,仅供参考;安装前建议先阅读原文。
SKILL.md 正文
First, decide whether the user wants to create a new scheduled task or change an existing one.
Updating an existing task
If the user wants to reschedule, edit the prompt, or pause/resume a task that already exists, call the update_scheduled_task tool with its taskId — do not call create_scheduled_task. Use list_scheduled_tasks if you need to look up the ID. When this session is itself a scheduled run, the current task's ID is the name attribute in the <scheduled-task name="…"> tag at the top of the conversation.
Creating a new task
You are distilling the current session into a reusable shortcut. 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
The create_scheduled_task tool description explains the options (cronExpression for recurring, fireAt for one-time, omit both for ad-hoc) and their formats. If the user didn't give a clear schedule, propose one and ask them to confirm before proceeding — don't rely on an approval prompt to catch a wrong guess, since task creation may be approved automatically in some permission modes.
Finally, call the create_scheduled_task tool.
质量与来源
- 所属仓库
- asgeirtj/system_prompts_leaks
- 仓库星标
- 6.9 万
- 最近更新
- 今天
- 采集时间
- 今天
- commit
- a09e0e708710
- 内容指纹
- sha256:e2155ad8525e7aa
- 文件路径
- Anthropic/claude-code/skills/anthropic-skills/schedule/SKILL.md