orchestration-run-analysis

Analyze GitHub Actions workflow runs and artifacts into a structured post-mortem report.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/intel-agency/convo-content-buddy-papa92 --skill orchestration-run-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestration-run-analysis
Source: https://github.com/intel-agency/convo-content-buddy-papa92/tree/main/.agents/skills/orchestration-run-analysis
Command: npx skills add https://github.com/intel-agency/convo-content-buddy-papa92 --skill orchestration-run-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a forensic, evidence-driven way to understand why an orchestrator run failed, stalled, or produced unexpected outcomes by mapping workflow runs, event routing, labels, and agent trace artifacts into a single coherent post-mortem.

Core Features & Use Cases

  • Timeline reconstruction: Enumerates Actions runs, triggers, durations, results, and job execution states.
  • Event routing trace: Replays orchestrator clause matching and identifies label or title mismatches that caused fallthroughs.
  • Inventory audits: Reviews issues, PRs, milestones, and project state against expected orchestration outcomes.
  • Artifact analysis & reporting: Collects trace artifact metadata and produces a structured markdown run report with root cause and recommendations.
  • Use Case: Investigate a deployed template repository when epics, issues, or PRs are missing or a workflow sequence stalled.

Quick Start

Analyze the orchestrator workflow runs for the specified owner/repo and time range and produce a structured markdown post-mortem report summarizing timeline, root cause, and recommendations.

Frequently Asked Questions about orchestration-run-analysis

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

FAQPage Schema
How do I analyze a stalled GitHub Actions orchestrator run?

To analyze a stalled orchestrator run, you reconstruct the workflow timeline by enumerating Actions runs, triggers, and job execution states. This process maps event routing and trace artifacts into a structured post-mortem report identifying the root cause.

Why does my workflow event routing drop issues with mismatched labels?

Workflow event routing drops issues when orchestrator clause matching encounters label or title mismatches. Tracing these event routing discrepancies against expected orchestration outcomes reveals why specific issues or PRs fell through.

What is the best way to generate a post-mortem for failed orchestration workflows?

The best way to generate a post-mortem for failed orchestration workflows is to collect trace artifact metadata and raw debrief documents. This reconstructs clause matching to produce an evidence-backed markdown run report with recommendations.

Do I need read access to GitHub artifacts to audit orchestrator runs?

Yes, you need read access to GitHub Actions run pages, issue and PR listings, workflow artifacts, and raw debrief documents. This access is required to inventory project state and reconstruct clause matching for the analysis.

Can I audit missing milestones and PRs in a deployed template repository?

Yes, you can audit missing milestones and PRs in a deployed template repository. The analysis reviews issues, PRs, milestones, and project state against expected orchestration outcomes to identify workflow sequence stalls.