← BROSH CRMCONTENT HISTORY
WHAT CHANGED
Update to BROSH CRM
Snapshot Nov 19, 2026 · 18:11 UTC · version 1.4.2
Collection source: downloaded plugin package.
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 JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Help a user get started with the BROSH CRM plugin: verify the connection, explain their actual CRM model, choose a relevant workflow, and complete a useful first task. Use for onboarding, setup orientation, or a BROSH plugin tour, not as a prerequisite for concrete CRM requests.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 254
}
],
"name": "brosh-onboarding",
"skill_md_contents": "---\nname: brosh-onboarding\ndescription: \"Help a user get started with the BROSH CRM plugin: verify the connection, explain their actual CRM model, choose a relevant workflow, and complete a useful first task. Use for onboarding, setup orientation, or a BROSH plugin tour, not as a prerequisite for concrete CRM requests.\"\n---\n\n# BROSH CRM Onboarding\n\nHelp the user reach a useful first outcome in their own BROSH workspace. Keep the tour short and adapt it to the user's role and goal. If the user already requested a concrete task, proceed with it and introduce only what they need.\n\n## Connection and context\n\n1. Discover the available BROSH tools and call `brosh_me` to verify the connection and user/workspace context. If authentication fails, describe the actual error and use the host's supported connect/reconnect flow when available. Do not ask for passwords, tokens, or API keys in chat, or claim a connection succeeded without a successful read.\n2. Read `brosh_available_tables` and a small relevant sample to explain the user's model. Avoid dumping all CRM data into a welcome message. Distinguish inaccessible data, empty tables, and failed queries.\n3. Infer the role and goal from the conversation. If neither is known, ask one short choice: find new customers, manage deals, understand an account, or improve CRM data. Continue the connection/schema checks while awaiting the choice when possible.\n4. Explain only useful model details: companies live in Accounts, people/leads in Contacts, sales deals in Opportunities with `type=\"Opportunity\"`, and tasks/interactions in Activity. Quotes/invoices may share Opportunities. Actual stages and fields vary by workspace.\n\n## Complete a first workflow\n\nChoose one useful result, reusing existing authorization. A general tour can show a small read-only account or pipeline example; it does not authorize sample leads, schema edits, imports, messages, or fake opportunities. If the CRM is empty, provide a clearly labeled draft example and the next real setup action instead of inserting demonstration data.\n\n| User goal | Workflow in this package |\n| --- | --- |\n| Find new ICP customers with emails/phones in a Contacts list | `brosh-ai-deal-hunter`; exact source `Deal Hunter` |\n| Prepare for an account meeting | `brosh-account-brief` |\n| Review open deals and next actions | `brosh-pipeline-review` |\n| Audit or clean existing records | `brosh-crm-data-hygiene` |\n| Configure fields or migrate another CRM | `brosh-crm-admin-migrator` |\n| Rank current business owners/founders as prospects | `brosh-lead-prospector` |\n| Research executive prospects by U.S. state | `brosh-ai-prospecting` |\n| Handle sales email conversations and follow-ups | `brosh-ai-sdr` |\n| Handle support tickets and responses | `brosh-ai-support` |\n| Market to existing customers | `brosh-ai-marketing` |\n| Research and create content | `brosh-ai-content-creator` |\n\nRead only the chosen installed skill's instructions. If it is unavailable, explain the missing workflow and use verified tools for the supported portion. Do not imply Salesforce or HubSpot needs to be installed for these BROSH workflows.\n\nExamples to adapt to the user's context:\n\n- \"Find 10 new customers matching our ICP, verify business emails and phones, and save them in a Deal Hunter contact list.\"\n- \"Brief me on this account before tomorrow's meeting.\"\n- \"Review my open deals closing this quarter and flag the next actions.\"\n- \"Audit our contacts for duplicates and missing company links without changing records.\"\n\n## Setup and completion\n\nIf setup is requested, discover current owners, currency, timezone, stages, required fields, lead sources, and relevant Contacts views. Use existing compatible settings. Make a concrete configuration plan and apply only the authorized supported changes, checking results afterward. Never assume one workspace's owner IDs, sender IDs, source defaults, or stages apply elsewhere.\n\nBROSH's core tools can read/create/update CRM records, modify supported fields, and send email. Do not imply that connecting BROSH also connects an email inbox, calendar, enrichment provider, or publishing platform. Inspect actual tools before claiming a feature is supported. Identify optional dependencies only for the chosen task; set up recurring runs only when asked and when the host supports scheduling.\n\nFinish with the verified connection state, completed first outcome, any actual blockers, and one or two relevant example requests. Distinguish recommendations from saved settings. Do not create tracking records or mark onboarding complete in CRM unless the user requested such a supported write.\n"
}SHA-256 of public snapshot: fa399a7d3cdd19c592b0fe74d8df34f0786297ad6734a94691e403a2bb3b0dcd