Scheduling widget

Triggered by the action bar's Schedule button (SKILL.md's "Schedule report" handler) — not auto-rendered. Load show_widget via ToolSearch and call it with title: "schedule_checkout_analysis" and loading messages ["Setting up schedule..."]. Only render where a scheduling mechanism actually exists in the environment.

The widget renders fully expanded. If a checkout-analysis task already exists for this domain (the action bar showed "Edit scheduled insights"), preselect the chips to match the existing schedule so the user is editing it, not recreating it.

<style>
.chip{padding:6px 14px;font-size:13px;font-weight:500;border-radius:100px;cursor:pointer;background:var(--color-background-primary) !important;border:1px solid var(--color-border-tertiary) !important;color:var(--color-text-secondary) !important;}
.chip.on{background:#E6F1FB !important;border:1.5px solid #185FA5 !important;color:#0C447C !important;}
.fcard{padding:14px 10px;font-size:13px;font-weight:500;text-align:center;border-radius:var(--border-radius-md);cursor:pointer;display:flex;flex-direction:column;align-items:center;gap:6px;background:var(--color-background-primary) !important;border:1px solid var(--color-border-tertiary) !important;color:var(--color-text-secondary) !important;}
.fcard.on{background:#E6F1FB !important;border:1.5px solid #185FA5 !important;color:#0C447C !important;}
.slabel{font-size:11px;font-weight:500;color:var(--color-text-secondary);text-transform:uppercase;letter-spacing:0.07em;margin:0 0 10px;}
</style>

<div style="border:0.5px solid var(--color-border-tertiary);border-radius:var(--border-radius-lg);background:var(--color-background-primary);overflow:hidden;">
  <div style="padding:16px 20px 20px;">
    <p style="font-size:15px;font-weight:500;color:var(--color-text-primary);margin:0 0 24px;">Schedule checkout analysis</p>

  <p class="slabel">Frequency</p>
  <div style="display:grid;grid-template-columns:repeat(3,1fr);gap:8px;margin-bottom:24px;" id="freq-wrap">
    <button class="fcard on" onclick="selectFreq(this)" data-value="weekly"><i class="ti ti-calendar" aria-hidden="true"></i>Weekly</button>
    <button class="fcard" onclick="selectFreq(this)" data-value="biweekly"><i class="ti ti-calendar-stats" aria-hidden="true"></i>Bi-weekly</button>
    <button class="fcard" onclick="selectFreq(this)" data-value="monthly"><i class="ti ti-calendar-month" aria-hidden="true"></i>Monthly</button>
  </div>

  <div id="day-section" style="margin-bottom:24px;">
    <p class="slabel">Day</p>
    <div style="display:flex;gap:8px;flex-wrap:wrap;">
      <button class="chip on" onclick="selectDay(this)" data-value="Monday">Mon</button>
      <button class="chip" onclick="selectDay(this)" data-value="Tuesday">Tue</button>
      <button class="chip" onclick="selectDay(this)" data-value="Wednesday">Wed</button>
      <button class="chip" onclick="selectDay(this)" data-value="Thursday">Thu</button>
      <button class="chip" onclick="selectDay(this)" data-value="Friday">Fri</button>
    </div>
  </div>

  <div style="margin-bottom:24px;">
    <p class="slabel">Time</p>
    <div style="display:flex;gap:8px;flex-wrap:wrap;" id="time-section">
      <button class="chip" onclick="selectTime(this)" data-value="7:00 AM">7 am</button>
      <button class="chip on" onclick="selectTime(this)" data-value="9:00 AM">9 am</button>
      <button class="chip" onclick="selectTime(this)" data-value="12:00 PM">12 pm</button>
      <button class="chip" onclick="selectTime(this)" data-value="5:00 PM">5 pm</button>
    </div>
  </div>

  <p class="slabel">Send to</p>
  <p style="font-size:12px;color:var(--color-text-tertiary);margin:0 0 10px;">At least one required. Only Email, Slack, and Notion — do not add any other options.</p>
  <div style="display:flex;gap:8px;flex-wrap:wrap;margin-bottom:28px;">
    <button class="chip" onclick="toggleChip(this)" data-value="email"><i class="ti ti-mail" style="font-size:14px;vertical-align:-1px;margin-right:4px;" aria-hidden="true"></i>Email</button>
    <button class="chip" onclick="toggleChip(this)" data-value="slack"><i class="ti ti-brand-slack" style="font-size:14px;vertical-align:-1px;margin-right:4px;" aria-hidden="true"></i>Slack</button>
    <button class="chip" onclick="toggleChip(this)" data-value="notion"><i class="ti ti-brand-notion" style="font-size:14px;vertical-align:-1px;margin-right:4px;" aria-hidden="true"></i>Notion</button>
  </div>

    <div style="display:flex;justify-content:flex-end;align-items:center;gap:12px;border-top:0.5px solid var(--color-border-tertiary);padding-top:16px;">
      <button onclick="sendPrompt('Skip scheduling for now')" style="padding:7px 16px;font-size:13px;font-weight:500;color:var(--color-text-secondary);background:transparent;border:none;cursor:pointer;">Skip</button>
      <button onclick="submitSchedule()" style="padding:7px 20px;font-size:13px;font-weight:500;color:var(--color-text-primary);background:var(--color-background-secondary);border:0.5px solid var(--color-border-secondary);border-radius:var(--border-radius-md);cursor:pointer;">Schedule analysis</button>
    </div>
  </div>
</div>

<script>
function toggleChip(el){el.classList.toggle('on');}
function selectDay(el){document.querySelectorAll('#day-section .chip').forEach(b=>b.classList.remove('on'));el.classList.add('on');}
function selectTime(el){document.querySelectorAll('#time-section .chip').forEach(b=>b.classList.remove('on'));el.classList.add('on');}
function selectFreq(el){
  document.querySelectorAll('#freq-wrap .fcard').forEach(b=>b.classList.remove('on'));
  el.classList.add('on');
  document.getElementById('day-section').style.display=el.dataset.value==='monthly'?'none':'block';
}
function submitSchedule(){
  const freq=document.querySelector('#freq-wrap .fcard.on')?.dataset.value||'weekly';
  const day=document.querySelector('#day-section .chip.on')?.dataset.value||'Monday';
  const time=document.querySelector('#time-section .chip.on')?.dataset.value||'9:00 AM';
  const delivery=[...document.querySelectorAll('[data-value="email"],[data-value="slack"],[data-value="notion"]')].filter(b=>b.classList.contains('on')).map(b=>b.dataset.value);
  if(!delivery.length){alert('Select at least one delivery method.');return;}
  sendPrompt('Schedule checkout analysis: frequency='+freq+', day='+day+', time='+time+', delivery='+delivery.join(' and '));
}
</script>

On submit

The widget renders once and never reloads — it shows all three delivery chips unconditionally, so connection is resolved here at submit time, not in the widget. When the user submits with their chosen channels:

For each chosen channel that isn't connected, connect it now via suggest_connectors with the appropriate UUID (Slack: 597f662f-36de-437e-836e-5a81013cbfbe; Notion: 69f3a300-cc60-48c4-b237-dfac56530dbf; Email/Gmail: search registry for "gmail").
Ask for any missing delivery details (email address, Slack channel, Notion page) if not already known.
Create or update the scheduled task with create_scheduled_task / update_scheduled_task (update if editing an existing one). Task name: checkout-analysis-[domain].

Scheduled task prompt

Run /checkout-analysis for [domain]. When the full analysis completes, do not show the triage-board widget — instead format the results as a [email/Slack/Notion] digest and send to [destination]. The digest has two parts: (1) an Overview block carrying the same stats shown above the cards, and (2) the ranked priorities, each with its own copyable Cowork prompt — do not collapse to a single generic prompt at the end.

Overview block — lead the digest with the overview stats (same as the board's Overview card): the funnel as a one-line text path (Added to cart 22,866 → Started checkout 42% → Payment 24% → Completed 23%), then Checkout completion, Mobile / Desktop conversion, Checkout errors, Median order, Discounted %. Include only populated stats (Principle 1).

Per-priority prompt — under each priority, give a copyable "Investigate" prompt that names that signal, so it carries context when pasted (it triggers the Investigate-click handler). Format:

Investigate this checkout signal: [Title] — [one-line finding] on [domain]. Dig into the why and what to do next.

Optionally end the whole digest with one re-run command to reopen the full board: /checkout-analysis on [domain].

Email: Subject Checkout analysis — [domain] — [date]. Open with the Overview block. Then each priority: title, one-line finding, "~N sessions affected", and its prompt under "Open Cowork and type:" wrapped in an HTML <code> tag to stop Gmail auto-linking the domain — e.g. Open Cowork and type: <code>Investigate this checkout signal: Cart-to-checkout leak — 58% of cart-adders never start checkout on atari.com. Dig into the why and what to do next.</code>

Slack: Lead *Checkout analysis — [domain]* — [date], then the Overview block as a short line. Each priority with title, finding, "~N sessions affected", and "Open Cowork and type:" followed by its prompt in a backtick code block so it's copyable.

Notion: Page titled Checkout analysis — [domain] — [date]. First a short Overview section with the stats. Then each priority as a callout block with title, finding, and "~N sessions affected", followed by a text line "Open Cowork and type:" and its prompt as a code block:

Open Cowork and type:
Investigate this checkout signal: Cart-to-checkout leak — 58% of cart-adders never start checkout on louloulollipop.com. Dig into the why and what to do next.

Scheduling widget