scheduled-tasks
Create, edit, run or audit scheduled, planned and adhoc tasks; cron, timezones and reminders.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- scheduled-tasks
- description
- Create, edit, run or audit scheduled, planned and adhoc tasks; cron, timezones and reminders.
02 资源文件 1
- 参考文档AGENTS.md878 B
03 SKILL.md 正文
Scheduler Tasks
Use the scheduler tool to manage saved tasks. Always inspect existing tasks before creating, updating, deleting, or running one.
Actions
list_tasks: optionalstate[],type[],next_run_within,next_run_afterfind_task_by_name:nameshow_task:uuidrun_task:uuid, optionalcontextupdate_task:uuid, optionalname,system_prompt,prompt,attachments[],schedule,timezone,plan[],state,dedicated_contextdelete_task:uuidcreate_scheduled_task:name,system_prompt,prompt, optionalattachments[],schedule,timezone,dedicated_contextcreate_adhoc_task:name,system_prompt,prompt, optionalattachments[],dedicated_contextcreate_planned_task:name,system_prompt,prompt, optionalattachments[],plan[],dedicated_contextwait_for_task:uuid
Schedule Fields
Schedules use cron-like fields. Do not put ISO datetimes into schedule.
minutehourdaymonthweekdaytimezone
Use IANA timezones such as Europe/Rome. Omit timezone to use the current user timezone. Planned task datetimes go in plan, not schedule, and should be ISO strings such as 2026-05-09T18:25:00.
For one future reminder, prefer create_planned_task with:
{
"action": "create_planned_task",
"name": "drink water",
"prompt": "Remind the user to drink water.",
"plan": ["2026-05-11T09:15:00"],
"dedicated_context": true
}
For a recurring or cron-shaped scheduled task, use create_scheduled_task with:
{
"action": "create_scheduled_task",
"name": "weekday stretch",
"prompt": "Remind the user to stretch.",
"schedule": {
"minute": "15",
"hour": "9",
"day": "*",
"month": "*",
"weekday": "1-5",
"timezone": "Europe/Rome"
},
"dedicated_context": true
}
Safety
- Do not create recursive task prompts that schedule more tasks.
- Do not run a task just because it is scheduled; run only if the user asks.
- Created tasks use a dedicated context unless
dedicated_contextis explicitlyfalse. - For destructive operations, identify the task by UUID after lookup.
Example
{
"tool_name": "scheduler",
"tool_args": {
"action": "find_task_by_name",
"name": "daily backup"
}
}
04 同仓库更多 Skills
system-lifecycle-designer
Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.
style-sampling
Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for "an episode of", "in the style of", "sample this style", 「用这个风格做一集」. One video to copy is reverse-any-video.
reverse-any-video
Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.
typescript-patterns
TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.
test-collaboration
Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit/integration/contract/E2E/smoke classification, bug-to-test regression protection, consumer/provider contract testing, test-necessity review, and pre-delivery evidence review.
story-lifecycle
Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira/Linear/Taiga but needs structured delivery tracking.