Update to 33CRM

{
  "description": "Produce a concise daily or weekly operating brief from 33CRM. Use when a company admin asks what happened today, this week, yesterday, or over a short operating window and wants sales, bookings, marketing, pipeline, and conversation signals in one brief.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 449
    }
  ],
  "name": "daily-weekly-admin-brief",
  "skill_md_contents": "    ---\n    name: daily-weekly-admin-brief\n    description: Produce a concise daily or weekly operating brief from 33CRM. Use when a company admin asks what happened today, this week, yesterday, or over a short operating window and wants sales, bookings, marketing, pipeline, and conversation signals in one brief.\n    ---\n\n    Use this skill for short recurring operating briefs.\n\nPeriod handling:\n1. If the user says today, use today's UTC calendar date as both date bounds where supported.\n2. If the user says yesterday, use yesterday as both bounds.\n3. If the user says this week or weekly, use the requested calendar week when clear; otherwise use the most recent 7 days and say so.\n4. If the user asks for a comparison, call the same report tools for the immediately preceding equal-length period.\n\nCore tools:\n- `sales_summary`\n- `get_sales_report`\n- `get_booking_report`\n- `get_marketing_report`\n- `get_conversation_report`\n- `pipeline_summary` when a current pipeline snapshot is useful\n\nOutput:\n- Period covered\n- What changed / what happened\n- Sales and lead pulse\n- Bookings and attendance\n- Marketing pulse\n- Conversation workload\n- Current pipeline snapshot when relevant\n- 3-5 attention items based only on observed data\n\nRules:\n- Reply in the user's language.\n- Distinguish current snapshots from period metrics.\n- Do not treat booked value as revenue or current amount paid as period cash flow.\n- Do not claim causation between Meta spend and CRM conversion unless the returned data directly supports it.\n- Do not read or summarize conversation content; only operational metadata is available.\n- If data is empty, stale, or pagination-limited, say so explicitly.\n- Read-only workflow; never claim to create, assign, send, book, or modify anything.\n"
}