Autonomy layerv0.1.0

schedule-recurring-agent

Creates repeat-safe standing work with an idempotent brief, justified cadence, per-run bound, and off-switch.

WORKFLOW / 05/schedule-recurring-agent <the recurring job> [schedule — e.g. 'weekday 9am' or 'hourly']
  1. 01

    Confirm the work is recurring and its autonomous action scope is authorized.

  2. 02

    Write a self-contained brief with deduplication, reporting, escalation, and a per-run cap.

  3. 03

    Choose the least-frequent cadence that still meets the work’s arrival window.

  4. 04

    Choose durable cloud routine or in-session cron honestly and confirm registration.

  5. 05

    Inspect for duplicates and tear the routine down when its stop condition is met.

operating envelope

Use it deliberately.

The shortest useful definition of where this skill helps—and where it should stay out of the way.

Use when

  • Triage, monitoring, audits, or digests recur on a real cadence.
  • A fresh memory-less agent must perform the same bounded job safely each run.
  • The job needs a durable routine or a deliberately session-scoped cron.

Do not use when

  • The work happens once now.
  • A current run only needs to wait once for an external signal; use watch-and-act.
  • The brief cannot deduplicate prior work or define teardown.

output contract

What must be true when it stops.

Produces

  • Registered routine or session-scoped cron
  • Self-contained idempotent job brief
  • Cadence rationale and per-run budget
  • Reporting, escalation, deduplication, and teardown contract

Guarantees

  • Every run starts memory-less but receives a complete, idempotent brief.
  • The schedule bounds frequency and budget-guard bounds each invocation.
  • Cadence follows the real arrival rate instead of maximum frequency.
  • Irreversible and externally visible actions require their own authorization.
  • Every routine has a teardown condition and reports even an honest nothing-to-do result.

Honest failure states

  • duplicate — an overlapping schedule already exists
  • not_idempotent — the brief would repeat or spam prior work
  • unbounded — no per-run cap exists
  • wrong_mechanism — the selected scheduler cannot meet the required durability

enforcement

Know which claims are executable.

Scripts are linked when this skill owns deterministic machinery. The remaining rules are explicit operating contracts and must not be marketed as hooks.

Procedural contract

This skill composes platform tools and verification evidence; it does not claim a dedicated guard script.

install and invoke

One skill, three honest surfaces.

skills.sh

Available

Universal skill installation, including Claude Code and Codex.

npx skills add https://github.com/ulpi-io/skills-autonomous-engineering --skill schedule-recurring-agent

Claude Code plugin

Available

Install the full plugin, then invoke /schedule-recurring-agent or let routing select it from context.

Claude installation →

Codex plugin

Work in progress

A work in progress on the codex-native-plugin branch — build it, start a new session, then invoke $autonomous-engineering:schedule-recurring-agent.

Codex installation →