Inspiration

Working on the technical crew for Pesta Tanglung at Universiti Kebangsaan Malaysia showed me how much coordination goes into a single live cue. A last-minute change can send the stage manager and AV crew back to three places: the run sheet for timing, the cue sheet for approval, and the production folder for the actual video. I built CueCheck around a question a stage manager might ask minutes before a show: Can we switch to the shorter video and still hit the finale on time?

What it does

CueCheck compares the current video with one proposed replacement. It calculates how much time each option has before the next fixed cue, checks the approval recorded in the AV cue sheet, and looks for the exact approved filename on the UGREEN AI NAS. It returns the decision, the evidence behind it, and the next action for the crew.

In my test scenario, there are 40 seconds before the finale. The current 95-second cut would run 55 seconds over. The proposed 30-second cut leaves 10 seconds to spare, but the production folder contains only a preview. CueCheck flags the swap as blocked and identifies the approved file the crew needs to add. Once they add it, the stage manager can rerun the check.

How I built it

I designed CueCheck as a read-only Uliya Skill using the official UGOS Skill Creation Tool. It delegates to the document expert to extract timing, durations and approval details from two selected PDFs, then to the file expert to confirm the exact asset in the authorized NAS folder. I used OpenAI Codex to assist with authoring and validation. The Round 1 package passed UGREEN’s static checker with zero errors or warnings. Live NAS validation is pending.

Challenges and what I learned

The hardest part was deciding what evidence is enough to call a swap ready. A similar filename is easy to mistake for the approved cut, and a folder the Skill cannot access tells us nothing about whether the file is there. Designing those cases taught me to make blocked and unverified distinct outcomes. A stage manager needs to know whether to fix a confirmed problem or ask someone to verify it.

Built With

Share this project:

Updates

Submission history