← BROSH CRMCONTENT HISTORY

Update to BROSH CRM

Snapshot Nov 19, 2026 · 18:11 UTC · version 1.4.2

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save BROSH CRM and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Identify and prioritize BROSH deals that need attention today: overdue commitments, unanswered customers, stalled engagement, close-date risks, and missing next steps. Use for a daily deal action queue; use pipeline review for aggregate pipeline or forecast reporting.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 262
    }
  ],
  "name": "brosh-deals-need-attention",
  "skill_md_contents": "---\nname: brosh-deals-need-attention\ndescription: \"Identify and prioritize BROSH deals that need attention today: overdue commitments, unanswered customers, stalled engagement, close-date risks, and missing next steps. Use for a daily deal action queue; use pipeline review for aggregate pipeline or forecast reporting.\"\n---\n\n# BROSH Deals Need Attention\n\nAnswer “Which deals need my attention today?” with a ranked, evidence-backed queue and a specific next action for each deal. The review itself is read-only. Treat screenshots as layout examples, never as live CRM records or authorization to send.\n\n## Establish the review scope\n\n- Discover the connected BROSH tools and their current argument schemas. Use `brosh_me` for workspace and user context, `brosh_available_tables` for supported fields and relationships, and `brosh_find` / `brosh_get` for records. Do not assume field or enum names beyond verified metadata.\n- Resolve “my” to the authenticated user's ownership. Respect a named owner, team, pipeline, or selected deal list. For an unqualified request, review accessible open deals and state that scope. If user-to-owner mapping is ambiguous, explain the limitation instead of silently showing another seller's deals.\n- Establish the as-of timestamp and the user's/team's timezone. “Today” means the local calendar date. Compare timestamp deadlines with the current time; date-only tasks due today are due today, not overdue before that day ends.\n- Query `opportunities` with `type=\"Opportunity\"`; quotes and invoices share that table and are not sales deals. Verify stage semantics and exclude confirmed won/lost records. Keep unknown stages in a separate unresolved group.\n- Fetch IDs, names, owner, account/contact, stage, amount/currency, close date, creation date, and supported next-step fields. Complete pagination and deduplicate IDs before claiming population counts. If limited by access or run size, label results as partial and state the reviewed count.\n\n## Gather evidence before flagging a deal\n\nRetrieve relevant tasks, emails, calls, meetings, and commitments through `activity`, using `opportunities` for the deal relationship and `person` for the contact. Resolve contacts and owners from actual IDs. Distinguish direct deal evidence from account-wide activity; do not attribute another deal's conversation to this one.\n\nReview enough activity history to support the applied time window. Separate completed interactions from planned tasks, cancelled meetings, automated notifications, email opens, delivery events, and record edits. `last_modified_date` does not establish customer engagement, stage age, or close-date slippage. Missing or inaccessible activity means evidence is incomplete, not that nothing happened.\n\nUse workspace thresholds and stage-specific expectations when available. Otherwise state these adjustable triage assumptions:\n\n| Signal | Default treatment |\n| --- | --- |\n| Unresolved customer question or overdue seller commitment | Urgent; cite the message/task and its timestamp or due date |\n| Open deal with a past close date | Urgent close-date review; do not move the date automatically |\n| Next step due today | Due today; show owner, action, and deadline |\n| Close date within 7 calendar days with no confirmed next step | At risk; verify the next milestone |\n| No substantive engagement for 30 calendar days | Potentially stalled only when reviewed history covers that interval |\n| Missing owner, contact, or next step | Needs information; recommend a specific internal repair |\n\nFor a deal younger than 30 days, absence of activity alone does not meet the 30-day stale threshold. If activity coverage is complete and there has never been an interaction, calculate the interval from deal creation and say so. If history is incomplete, mark engagement unknown. Future agreed meetings, buyer-requested pauses, and not-before dates may explain silence; show them and avoid suggesting premature outreach. A manual “stalled” CRM status and an inferred stale-engagement flag are distinct.\n\nUse MEDDPICC or another qualification score only when the tenant actually stores the relevant fields and their definitions. Display a stored score or calculate completion from the verified criteria, show missing criteria, and identify the calculation. Do not invent an 8-part score from notes or copy the sample score from a screenshot. Missing qualification data is unknown, not a zero score.\n\n## Rank and present\n\nPrioritize unresolved customer requests and overdue commitments, then time-sensitive close risks and today's next steps, then stale engagement and missing information. Explain competing signals. Use deal value only as a secondary criterion within comparable currencies; do not rank raw mixed-currency amounts or invent a probability of loss.\n\nLead with the scope, as-of date/timezone, number of reviewed open deals, and number of unique deals needing attention. Count each deal once even if it has several flags; reason counts can overlap. Show a compact table:\n\n`Deal / record ID | Owner / contact role | Stage | Last substantive activity | Attention reason and dated evidence | Priority | Recommended next step / timing`\n\nInclude amount/currency, close date, or qualification completion when useful and supported. Cite returned CRM links, or table and record IDs if links are unavailable. Label inferred classifications. Use a native CRM card only if the connected tools support it; otherwise use a Markdown table. Do not fabricate working buttons, links, or a custom CRM UI.\n\nWhen none qualify, say “No deals flagged in the reviewed scope” and disclose missing evidence. Never label unreviewed deals on track.\n\nFor outreach-ready items, offer personalized follow-up drafts through `brosh-deal-follow-up`. Carry forward the selected deal IDs, evidence, timing constraints, and reasons; recheck them before sending. A “yes” to drafting authorizes drafting only. Internal data repairs, tasks, stage changes, and messages require a user request or existing authorization for those actions; recommendations alone do not authorize them.\n"
}

SHA-256 of public snapshot: 683c06c69ecc9ba916034fda1a72d5aa6c04c7853fbb3b13e7326758e969bf58