e-volv

Agent Ops playbook

PlaybookHealthCheck

Weekly league table of per-playbook execution health with failure rate, cost-per-success, and specific fix proposals for the worst performers.

Weekly, computes per-playbook health across the workspace — execution count, success rate, median duration, median cost, and the most common failure step — ranks playbooks by failure rate and cost-per-successful-run, and proposes specific fixes for the worst performers. Also surfaces playbooks with zero executions as adoption gaps.

Identifier
playbook-health-check
Version
1.0.0
Steps
3
Triggers
1
  • playbook
  • health
  • metrics
  • agent-ops
  • weekly
  • automated

When it runs

Scheduleschedule.weekly
Schedule
Every Monday at 07:00 UTC 0 7 * * 1
Timezone
UTC

The pipeline

The graph below is the one the workflow opens with in the builder — same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.

React Flow
  1. 01
    Weekly Schedule (Monday 07:00 UTC)trigger

    The event that starts the run.

  2. 02
    Analyse Playbook Healthagent.run

    One agent works the task with its toolkit.

  3. 03
    File Health Check Ticketticket.create

    Opens a ticket on the connected tracker.

The agent

Playbook Health Analyst

Base type
Senior Developer
Temperature
0.2
Max iterations
50
Tools
8

Filesystem · 2

  • read_fileRead File · read
  • list_dirList Directory · read

Memory · 2

  • memory_writeWrite Memory · write
  • memory_readRead Memory · read

Terminal · 1

  • run_terminal_cmdRun Terminal Command · write

Code search · 1

  • code_searchCode Search · read

Tickets · 1

  • create_ticketCreate Ticket · write

Status · 1

  • update_statusUpdate Status · write