Automation Config
Apps & Automationautomation-configAutomation 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.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/alfredxw/denova/blob/HEAD/skills/automation-config/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/automation-config, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Automation Config
Use this skill before calling write_automations.
Workflow
- Call
list_automationsfirst. For updates, callread_automationsfor the target IDs before writing. - Use
write_automationsonly for module-level changes. Do not editautomations/tasks.jsondirectly. - For
create, provide a completetaskobject with clearname,scope,template,prompt, trigger policy, write policy, and output policy. - For
update, preserve fields not requested by the user. Send the existingidinop.idortask.id. - For
delete, only sendop: "delete"after the user explicitly asked to delete the task.
Task Shape
Important task fields:
scope:workspacefor the current book, oruserfor reusable personal automations.enabled: boolean.name: user visible task name.template: one ofmemory_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 ofread_only,confirm_write,auto_write.write_scope: one ofnone,lore,file,lore_and_file.output_policy: one ofrun_record_only,optional_file.output_path: required only whenoutput_policyisoptional_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 likedaily_revieworchapter_batch_review.type: one ofmanual,schedule,semantic,chapter_batch.enabled: boolean.name: optional user-visible label.notify_policy:inboxorsilent. Schedule defaults tosilent; content triggers default toinbox.schedule: required forscheduletriggers.semantic_condition: required for usefulsemantictriggers.chapter_batch_size: positive integer forchapter_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:
manualdailyweeklymonthlyevery_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_scopeand a prompt that names the exact file or lore boundary. - Use
workspacescope unless the user says the automation should apply across books.