How do I install the Automation Scheduler skill?

Run npx skillmds@latest add gonzalezpazmonica/automation-scheduler in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Automation Scheduler safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Automation Scheduler?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Automation Scheduler free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Automation Scheduler?

gonzalezpazmonica (@gonzalezpazmonica) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Automation Scheduler by gonzalezpazmonica

Name: Automation Scheduler
Rating: 4.2 (5 reviews)
Author: gonzalezpazmonica

Automation Scheduler

Usar cuando se crean, gestionan o ejecutan automatizaciones programadas: morning briefs, weekly reports, PR stale checks, dependency scans, memory consolidation, drift audits. Triggers: programa una tarea, automatiza esto, crea una automatizacion, scheduled task, ejecuta cada dia, /automations, init-defaults.

File contents

automation-scheduler

Pipeline: LIST, CREATE, TEST, MONITOR, MANAGE.

Default Tasks

6 tareas predefinidas via savia-automations.sh init-defaults:

Tarea	Schedule	Skill	Agente
morning-brief	0 9 * * 1-5	sprint-management	azure-devops-operator
pr-stale-check	0 10 * * *	none	azure-devops-operator
drift-daily	0 7 * * *	none	drift-auditor
memory-consolidation	0 2 * * *	savia-memory	memory-agent
weekly-report	0 8 * * 5	weekly-report	none
dependency-cve-scan	0 8 * * 1	dependency-scanner	none

Scoped Approvals

Cada tarea declara always_allowed_tools. El runner rechaza cualquier tool no incluida.

Politicas

Run-once-catch-up: runs perdidos se ejecutan al reiniciar
Skip-on-overlap: una tarea en ejecucion no se lanza otra vez
Max concurrent: 3 runs simultaneos
Tick interval: 30s por defecto

Goals durables y heartbeats claimed-due (lección SE-347 / PMA)

Goals (bash scripts/savia-goals.sh): objetivo con presupuesto (tokens + wall-clock) y estado durable en ~/.savia/goals/. Regla: SOLO complete marca éxito (goal.complete() es el único final válido); progress acumula tokens/segundos/continuations; abandon para cerrar sin éxito. Usa goals en tareas largas (overnight, migraciones, releases).
Heartbeats claimed-due (savia-goals.sh heartbeat claim-due): un tick pendiente NO se reentrega tras crash (si un runner murió tras marcar last_claimed, otro runner no lo reclama de nuevo); ticks perdidos coalescen (solo se entrega el más reciente). Añade heartbeats con heartbeat add --every <secs> --prompt <text> para tareas de larga duración.

Data

Tasks: .savia/automations/tasks.json
Runs: .savia/automations/runs/{task_id}/
Output: output/automations/{task_id}/{run_id}.md
Goals/heartbeats: ~/.savia/goals/ (savia-goals.sh)

CLI Reference

savia-automations.sh list [--enabled] [--due] savia-automations.sh show savia-automations.sh create --name --schedule --instructions savia-automations.sh run savia-automations.sh disable|enable savia-automations.sh delete savia-automations.sh history [--last N] savia-automations.sh output savia-automations.sh init-defaults

---name: automation-schedulerdescription: Usar cuando se crean, gestionan o ejecutan automatizaciones programadas: morning briefs, weekly reports, PR stale checks, dependency scans, memory consolidation, drift audits. Triggers: programa una tarea, automatiza esto, crea una automatizacion, scheduled task, ejecuta cada dia, /automations, init-defaults.---# automation-schedulerPipeline: LIST, CREATE, TEST, MONITOR, MANAGE.## Default Tasks6 tareas predefinidas via savia-automations.sh init-defaults:| Tarea | Schedule | Skill | Agente ||-------|----------|-------|--------|| morning-brief | 0 9 * * 1-5 | sprint-management | azure-devops-operator || pr-stale-check | 0 10 * * * | none | azure-devops-operator || drift-daily | 0 7 * * * | none | drift-auditor || memory-consolidation | 0 2 * * * | savia-memory | memory-agent || weekly-report | 0 8 * * 5 | weekly-report | none || dependency-cve-scan | 0 8 * * 1 | dependency-scanner | none |## Scoped ApprovalsCada tarea declara always_allowed_tools. El runner rechaza cualquier tool no incluida.## Politicas- Run-once-catch-up: runs perdidos se ejecutan al reiniciar- Skip-on-overlap: una tarea en ejecucion no se lanza otra vez- Max concurrent: 3 runs simultaneos- Tick interval: 30s por defecto## Goals durables y heartbeats claimed-due (lección SE-347 / PMA)- **Goals** (`bash scripts/savia-goals.sh`): objetivo con presupuesto (tokens + wall-clock) y estado durable en `~/.savia/goals/`. Regla: SOLO `complete` marca éxito (`goal.complete()` es el único final válido); `progress` acumula tokens/segundos/continuations; `abandon` para cerrar sin éxito. Usa goals en tareas largas (overnight, migraciones, releases).- **Heartbeats claimed-due** (`savia-goals.sh heartbeat claim-due`): un tick pendiente NO se reentrega tras crash (si un runner murió tras marcar `last_claimed`, otro runner no lo reclama de nuevo); ticks perdidos **coalescen** (solo se entrega el más reciente). Añade heartbeats con `heartbeat add --every <secs> --prompt <text>` para tareas de larga duración.## Data- Tasks: .savia/automations/tasks.json- Runs: .savia/automations/runs/{task_id}/- Output: output/automations/{task_id}/{run_id}.md- Goals/heartbeats: ~/.savia/goals/ (savia-goals.sh)## CLI Referencesavia-automations.sh list [--enabled] [--due]savia-automations.sh show <task-id>savia-automations.sh create --name <n> --schedule <cron> --instructions <text>savia-automations.sh run <task-id>savia-automations.sh disable|enable <task-id>savia-automations.sh delete <task-id>savia-automations.sh history <task-id> [--last N]savia-automations.sh output <task-id> <run-id>savia-automations.sh init-defaults

Frequently asked questions