routines plugins

by Mohit Aggarwal

Put recurring rituals on autopilot: charter what to automate, schedule it on any runner (Claude Code routines, cron, n8n, GitHub Actions), and make every run delta-aware so it reports what changed, not what it already said. Ships with the recurring skills worth scheduling.

by Melodic Software

Contracts for governed autonomous agent operation: role topology, binding seam, telemetry, return accounting, trigger dispatch, a per-work-class guardrail matrix, a standing-routine catalog, and a runner charter. A guided setup skill writes an org's binding, wires OTLP telemetry (file default), human-attested return capture, and signal adapters behind one governed dispatch entrypoint, binds the guardrail matrix to isolation substrates after a live probe, and schedules routines.

by Garret

Jack into any OpenAPI spec — full CLI with AI-agentic workflow automation

by Artience

Cowork-optimized build of Artibot — marketing, content, data, design, CRO/SEO, long-form writing, Claude Design, Routines, Ultraplan, Monitor, and swarm intelligence for knowledge workers

by Memory Daemon contributors

Safely manage memory-daemon routines and connector prompt overrides

by Job Schepers

The unattended lane, stacked on delivery: the nineteen schedule-* skills that run with nobody watching, plus init and update, plus the catalog of triggers that fires them. Seventeen schedulable entry points that pick their own input and run a flow, a review, a check, a sweep, or a report — devbook validate, devbook verify, devbook update, instruction review, issue sweep, merge review, morning brief, package update, performance review, review, security review, tech update, week starter, weekly cost analysis, weekly retro, weekly update, and what's new — and fourteen trigger definitions naming a target, a cadence, the plugins that target needs, and the prompt for a local routine that runs unattended on this machine, never a cloud session. delivery-schedule:init creates them through whatever scheduler the live session exposes and stamps the selection under components.schedule, and delivery-schedule:update keeps them level with it; schedule-status reads their runs and logs; schedule-run fires one now. One capability, two host names: Routines in Claude Code, Automations in the GitHub Copilot app. Depends on delivery and names devbook: a trigger whose target is not enabled is reported and skipped, never scheduled.

by Job Schepers

The unattended lane, stacked on delivery: the eleven schedule-* skills that run with nobody watching, plus install, plus the catalog of triggers that fires them. Nine schedulable entry points that pick their own input and run a flow or a review — bug fix, merge review, package update, performance review, review, security review, week starter, weekly cost analysis, and what's new — and six trigger definitions naming a target, a cadence, the plugins that target needs, and the prompt for a cloud session that starts with nothing but the repository. delivery-schedule:install creates or updates them through whatever scheduler the live session exposes and records the selection under components.schedule; schedule-status reads their runs and logs; schedule-run fires one now. One capability, two host names: Routines in Claude Code, Automations in the GitHub Copilot app. Depends on delivery and names devbook: a trigger whose target is not enabled is reported and skipped, never scheduled.