Update to ServeStack

{
  "description": "A short sales briefing for a connected ServeStack restaurant — yesterday (or another period) versus a matching earlier period, top items, busy hours, and one or two suggestions.",
  "included_files": [],
  "name": "daily-briefing",
  "skill_md_contents": "---\nname: daily-briefing\ndescription: A short sales briefing for a connected ServeStack restaurant — yesterday (or another period) versus a matching earlier period, top items, busy hours, and one or two suggestions.\n---\n\n1. Call `get_owner_context`; if the owner has several locations, ask which one (or brief each separately — never add different locations together).\n2. Call `get_sales_summary` (default: yesterday vs the same weekday last week).\n3. Report: orders, net sales and average order with the change versus the comparison, the top items and the busiest hours. Always state the period, time zone and that these are online orders through ServeStack only — never \"total restaurant sales\", never \"profit\".\n4. Pass on every warning the tool returns (marketplace orders not included, today still in progress, test orders left out).\n5. Offer at most two concrete, low-risk suggestions tied to the numbers (e.g. promote a top item at the slow hour). Present changes in the numbers as what happened, not why — correlation isn't cause.\n6. If `get_connection_status` shows something needs attention, mention it with its fix link.\n"
}