What problem does it solve? Recurring agent briefings often fail silently: the scheduler fires but execution fails, a report is generated but never delivered, or a duplicate trigger is misread as a broken job. This Skill provides a disciplined workflow for creating self-contained scheduled briefings and diagnosing failures across four independent layers: trigger, execution, artifact, and delivery. ## Core Features & Use Cases - Creation Workflow: Build self-contained cron prompts with exact source identifiers, pagination scope, timezone, and failure behavior, then validate the live data source before scheduling. - Four-Layer Verification: Independently verify trigger, execution, artifact, and delivery instead of trusting a single job status field. - Run Diagnostics: Use the bundled decision tree and command sequence to classify issues like unacquired fire claims, unresolved origin channels, and skipped deliveries. - Use Case: Set up a daily Jira work-queue digest that queries live data, persists a report, and delivers it to a chat destination, then troubleshoot why a run completed but no message appeared. ## Quick Start Use the scheduled-briefing-operations skill to create a recurring weekday Jira digest job and verify its trigger, execution, artifact, and delivery layers.
