automations
GitHub用于创建、管理和运行DotCraft自动化工作流，支持定时提醒、重复任务及会话跟进。涵盖定义构建、状态管理及生命周期控制。
Trigger Scenarios
Install
npx skills add DotHarness/dotcraft --skill automations -g -y
SKILL.md
Frontmatter
{
"name": "automations",
"description": "Create, inspect, update, pause, resume, run, or delete DotCraft automations using the Automation tool. Use for reminders, recurring work, scheduled monitoring, and conversation follow-ups.",
"allowed-tools": "Automation"
}
Automations
Use Automation for work that should run later or repeatedly. Keep the user's requested task and timing in the editable definition; do not create a second workflow inside the prompt.
Create
- Use
threadfor follow-ups that depend on this conversation andindependentfor standalone work that starts a fresh conversation each run. - Resolve the schedule and, for calendar schedules, its time zone. Ask only when timing is genuinely ambiguous.
- Call
Automationwithaction: "create"and one complete definition.
| Kind | Required schedule fields |
|---|---|
at |
kind, absolute ISO 8601 string at |
every |
kind, positive everyMs |
daily, weekdays |
kind, hour, minute, timeZone |
weekly |
kind, hour, minute, timeZone, ISO weekday days |
Example:
{"action":"create","automation":{"name":"Build reminder","prompt":"Check the build and summarize failures.","status":"active","executionMode":"independent","schedule":{"kind":"at","at":"2030-01-15T09:00:00Z"},"notificationPolicy":"all"}}
schedule.at is a string, never a CLR-style object. notificationPolicy belongs inside automation. Keep unrelated schedule fields out. Omit workspaceMode and agentProfileId when unset; approvalPolicy is workspaceScope or fullAuto. Thread mode binds the current conversation when targetThreadId is omitted. Independent Git work defaults to a new worktree per run. Notifications default to important changes for thread mode and every result for independent mode.
Manage
Use list or read before changing a definition when its version is unknown. Updates require expectedVersion. Use pause, resume, or delete for lifecycle changes. Completed is assigned by DotCraft after a one-shot run and is read-only. run queues an execution; report it as queued.
Use supported schedule fields instead of arbitrary RRULE expressions. Do not retry task execution because result delivery failed.
Version History
- 2d7cea6 Current 2026-09-22 05:27
