# Automation Config

> Automation Config is an Agent Skill for apps & automation published in the alfredxw/denova repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use when config_manager creates or updates Denova automation task JSON through automation tools.

- Skill name: `automation-config`
- Category: [Apps & Automation](https://www.openparable.com/skill/apps-automation/1)
- Source: https://github.com/alfredxw/denova/blob/HEAD/skills/automation-config/SKILL.md
- Repository: alfredxw/denova (485 GitHub stars when collected)

## SKILL.md

# Automation Config

Use this skill before calling `write_automations`.

## Workflow

1. Call `list_automations` first. For updates, call `read_automations` for the target IDs before writing.
2. Use `write_automations` only for module-level changes. Do not edit `automations/tasks.json` directly.
3. For `create`, provide a complete `task` object with clear `name`, `scope`, `template`, `prompt`, trigger policy, write policy, and output policy.
4. For `update`, preserve fields not requested by the user. Send the existing `id` in `op.id` or `task.id`.
5. For `delete`, only send `op: "delete"` after the user explicitly asked to delete the task.

## Task Shape

Important task fields:

- `scope`: `workspace` for the current book, or `user` for reusable personal automations.
- `enabled`: boolean.
- `name`: user visible task name.
- `template`: one of `memory_consolidation`, `review`, `continue_writing`, `custom_prompt`.
- `prompt`: the task instruction that the automation agent will run.
- `model_profile_id`: optional model profile ID. Leave empty to inherit automation/default settings.
- `schedule`: structured schedule. Keep it consistent with schedule triggers.
- `triggers`: array of trigger definitions.
- `write_mode`: one of `read_only`, `confirm_write`, `auto_write`.
- `write_scope`: one of `none`, `lore`, `file`, `lore_and_file`.
- `output_policy`: one of `run_record_only`, `optional_file`.
- `output_path`: required only when `output_policy` is `optional_file`.

The backend derives legacy `write_policy` and `default_action_policy`; do not rely on trigger-level action policy.

## Trigger Shape

`triggers` contains objects with:

- `id`: stable identifier. Use meaningful IDs like `daily_review` or `chapter_batch_review`.
- `type`: one of `manual`, `schedule`, `semantic`, `chapter_batch`.
- `enabled`: boolean.
- `name`: optional user-visible label.
- `notify_policy`: `inbox` or `silent`. Schedule defaults to `silent`; content triggers default to `inbox`.
- `schedule`: required for `schedule` triggers.
- `semantic_condition`: required for useful `semantic` triggers.
- `chapter_batch_size`: positive integer for `chapter_batch`; default is 5.

Do not set `action_policy` on triggers. Effective execution behavior comes from `write_mode`.

## Schedule Shape

`schedule.kind` must be one of:

- `manual`
- `daily`
- `weekly`
- `monthly`
- `every_hours`

Common fields:

- `hour`: 0-23.
- `minute`: 0-59.
- `weekday`: 0-6 for weekly schedules, where 0 is Sunday.
- `day_of_month`: 1-31 for monthly schedules.
- `every_hours`: 1-168 for interval schedules.

`cron` is generated by the backend. Leave it empty unless you are preserving an existing value.

## Safe Defaults

- Review-only tasks: `write_mode: "read_only"`, `write_scope: "none"`, `output_policy: "run_record_only"`.
- File-writing tasks: prefer `write_mode: "confirm_write"` unless the user explicitly asks for unattended writes.
- Auto-write tasks must have a narrow `write_scope` and a prompt that names the exact file or lore boundary.
- Use `workspace` scope unless the user says the automation should apply across books.

---

Source: https://www.openparable.com/skill/apps-automation/automation-config (OpenParable). Cite the canonical URL above.
