opus-clips-performance

What problem does it solve?

You want to know how your OpusClip-scheduled clips performed on each platform, but the manifests record what was scheduled—not the engagement results.

Core Features & Use Cases

• Per-clip engagement reporting: Generates a markdown report with one section per clip, including score, duration, scheduled fan-out, and fetched engagement (at least for YouTube today).
• Manifest backfill for engagement: Updates each manifest’s scheduled_posts[] entries with an engagement block when available, or leaves a pending_task stub for platforms not yet wired.
• Robust YouTube joining: Joins scheduled posts to YouTube analytics via [opus:<clip_id>] tag lookup first, and then falls back to a ±2 hour time-window match biased by closest duration.
• Use case: After OpusClip posts have had time to ingest analytics, generate a report to answer “which clips landed and how did they do?” and feed those results into downstream prioritization.

Quick Start

Run opus-clips-performance to process all manifests whose newest scheduled post is at least 24 hours old and produce per-clip performance reports (YouTube engagement will be filled in).