optimize-runbook

Analyze Jetty run trajectories and generate cited RUNBOOK.md edits.

3|2|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/jettyio/jettyio-skills --skill optimize-runbook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: optimize-runbook
Source: https://github.com/jettyio/jettyio-skills/tree/main/skills/optimize-runbook
Command: npx skills add https://github.com/jettyio/jettyio-skills --skill optimize-runbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes historical Jetty workflow runs to identify actionable improvements and produce concrete, evidence-backed edits to your RUNBOOK.md.

Core Features & Use Cases

  • Pattern-based analysis across trajectories to surface recurring issues and opportunities for improvement.
  • Generation of precise, exact runbook edits with citations to the trajectory steps that motivated them.
  • Support for both interactive and headless modes, with clear versioning and guardrails to ensure safe updates.

Quick Start

Use this skill to analyze a loaded RUNBOOK.md against recent Jetty trajectories and generate concrete edits.

Frequently Asked Questions about optimize-runbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze past workflow runs to improve my runbook?

Analyzing past workflow runs to improve your runbook involves identifying recurring issues in Jetty trajectories, such as consistent failures or iteration waste, and generating precise before/after edits with citations for your RUNBOOK.md.

What kind of workflow patterns can I detect from run trajectories?

You can detect patterns such as consistent failures, iteration waste, and timeouts by analyzing run trajectories. The Skill surfaces these recurring issues to pinpoint specific opportunities for runbook improvements.

How do I generate precise edits for a RUNBOOK.md based on historical data?

Generating precise edits for a RUNBOOK.md based on historical data requires analyzing run trajectories to produce exact before/after changes with citations. The Skill outputs a patch-ready runbook update complete with a version bump when appropriate.

Can I use runbook analysis in headless mode without manual interaction?

Yes, you can use runbook analysis in headless mode. The Skill supports both interactive and headless modes, applying clear versioning and guardrails to ensure safe RUNBOOK.md updates without manual interaction.

What is included in the output when analyzing run trajectories for runbook improvements?

The output for runbook improvements includes a structured payload for instrumentation, exact before/after edits with citations, and a patch-ready RUNBOOK.md update complete with a version bump when appropriate.