Menu
Use when config_manager creates or updates Denova automation task JSON through automation tools.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/alfredxw/denova --skill automation-configThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
Based on SOC occupation classification
| name | automation-config |
| description | Use when config_manager creates or updates Denova automation task JSON through automation tools. |
| agent | config_manager |
Use this skill before calling write_automations.
list_automations first. For updates, call read_automations for the target IDs before writing.write_automations only for module-level changes. Do not edit automations/tasks.json directly.create, provide a complete task object with clear name, scope, template, prompt, trigger policy, write policy, and output policy.update, preserve fields not requested by the user. Send the existing id in op.id or task.id.delete, only send op: "delete" after the user explicitly asked to delete the task.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.
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.kind must be one of:
manualdailyweeklymonthlyevery_hoursCommon 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.
write_mode: "read_only", write_scope: "none", output_policy: "run_record_only".write_mode: "confirm_write" unless the user explicitly asks for unattended writes.write_scope and a prompt that names the exact file or lore boundary.workspace scope unless the user says the automation should apply across books.