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
higgsfield-websites
Build, edit, and deploy full-stack websites, apps and games via the Higgsfield CLI (`higgsfield website …`). Each is a React 19 + TanStack Start SSR app in one Cloudflare Worker (D1/R2/KV/DO/Containers). THREE product types, picked via `--type` on create: `website` (standalone, no Higgsfield integration — references/website-flow.md), `app` (Sign in with Higgsfield + fnf SDK, Quanta — references/app-flow.md), `game` (realtime multiplayer rooms — references/game-flow.md). Routes to the right flow; each carries its own rules and deploy/publish gates. Use when: "build me a website", "make a landing page", "create a web app", "build a SaaS dashboard / portfolio", "make me a game", "deploy this site", "publish". Also owns GAME ART: "make a spritesheet", "tileable texture", "animate a 3D character", game music/SFX — see the game-* references. NOT for: single image/video/audio generation (higgsfield-generate), product photos (higgsfield-product-photoshoot), marketplace cards (higgsfield-marketplace-cards).
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback