← 33CRMCONTENT HISTORY

Update to 33CRM

Snapshot Oct 24, 2026 · 13:38 UTC · version 1.1.1

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save 33CRM and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Create a management-level 33CRM brief across sales, pipeline, bookings, marketing, and conversation operations. Use when an owner, CEO, or company admin asks for an executive overview, business pulse, management summary, or cross-functional CRM performance brief.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 454
    }
  ],
  "name": "executive-crm-brief",
  "skill_md_contents": "    ---\n    name: executive-crm-brief\n    description: Create a management-level 33CRM brief across sales, pipeline, bookings, marketing, and conversation operations. Use when an owner, CEO, or company admin asks for an executive overview, business pulse, management summary, or cross-functional CRM performance brief.\n    ---\n\n    Use this skill for a cross-functional executive view of the authenticated company.\n\nCore workflow:\n1. Resolve the requested period. If the user gives no period, use the most recent 30 days for period reports and clearly label `pipeline_summary` as a current snapshot.\n2. Call `sales_summary` for lead-cohort performance.\n3. Call `get_sales_report` for deal count, booked value, amount paid to date, stage, and owner breakdowns.\n4. Call `pipeline_summary` for the current pipeline snapshot.\n5. Call `get_booking_report` for booking volume and attendance.\n6. Call `get_marketing_report` for stored Meta delivery/spend by ad account.\n7. Call `get_conversation_report` for conversation volume by channel/status.\n8. Use pagination or narrower filters if a tool says results are incomplete.\n\nOutput:\n- Executive summary\n- Key commercial metrics\n- Pipeline position\n- Booking/attendance position\n- Marketing delivery\n- Conversation workload\n- Items needing management attention\n- Data caveats\n\nRules:\n- Reply in the user's language.\n- Keep lead metrics and deal metrics separate; they are different populations.\n- `booked_value` is agreed deal value, not recognized revenue.\n- `amount_paid_to_date` is the current collected amount on deals in the selected deal cohort, not cash received during the period.\n- Meta provider leads are not CRM leads and must not be treated as directly attributed conversions.\n- Stored Meta data may be stale; do not imply a live provider refresh.\n- Conversation tools return operational metadata and counters, not message bodies.\n- Do not infer clinical, medical, treatment, or patient outcomes.\n- Do not invent benchmarks, targets, trends, or causes that are not supported by the returned data.\n- This workflow is read-only. Never imply that CRM records were changed.\n"
}

SHA-256 of public snapshot: f8a3f96a6df24cfb3b6df0a9aa63b67e15e97986a3a7f114952e6dacae0cbfb6