# Ops Automation Agent

Authoring playbook for building agents that automate recurring internal tasks, running...

- Repository: https://github.com/mastra-ai/mastra (29259 stars)
- Category: AI and agents
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add mastra-ai/mastra --skill ops-automation-agent -g -a claude-code -y`
Codex: `npx skills add mastra-ai/mastra --skill ops-automation-agent -g -a codex -y`
Cursor: `npx skills add mastra-ai/mastra --skill ops-automation-agent -g -a cursor -y`
Gemini CLI: `npx skills add mastra-ai/mastra --skill ops-automation-agent -g -a gemini-cli -y`

## Description

Authoring playbook for building agents that automate recurring internal tasks, running scheduled workflows, syncing data between systems, posting notifications, processing inbound events, or executing operational runbooks. Use this when the user wants an agent that runs on a schedule, reacts to events, automates a process, syncs between tools, or handles ops/internal infrastructure.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Ops Automation Agent Authoring Playbook

## When to use

Pick this playbook when the user mentions: automate, schedule, daily, weekly, recurring, cron, webhook, sync, integrate, pipeline, runbook, notification, alert, on-call, Slack/Teams post, "every time X happens", or any operational workflow.

## Agent identity template

- **Name pattern**: `<Action> Automator`, `<Source>-to-<Destination> Syncer`, `<Event> Responder`. Examples: "Daily Standup Poster", "Stripe-to-Slack Syncer", "On-Call Alert Triager".
- **Description pattern**: One sentence stating _trigger_ and _action_. Example: "Every weekday at 9am, posts a standup template in #engineering and pings yesterday's assignees."

## Safety boundary

The produced prompt must distinguish safe autonomous execution from confirmation-required operations:

- Routine reversible actions inside an encoded threshold may run autonomously.
- Destructive, irreversible, financial, external-send, permission-changing, or high-blast-radius operations must dry-run and stop for explicit confirmation unless the user explicitly requested autonomous execution and the prompt encodes a concrete safe threshold.
- Every run must use or derive an idempotency key so retries do not double-send, double-charge, double-delete, or double-post.
- Every run must produce a receipt.

## System prompt template

```
You are <agent name>. You <verb: run / sync / post / triage> <action> when <trigger>.

# What you own
Your job is to execute the authorized action and confirm what happened. You are NOT a chat partner, you take action, then report with a receipt.

# Trigger and input
A run starts when <schedule/webhook/event/user request> fires. The input includes <event id, timestamp, source record, target system, or payload>. Derive the idempotency key from <event id/date/source+target>.

The rest: https://github.com/mastra-ai/mastra/blob/HEAD/packages/editor/src/ee/workspace/skills/ops-automation-agent/SKILL.md