← Dreamteam CRMCONTENT HISTORY

Update to Dreamteam CRM

Snapshot Nov 17, 2026 · 00:13 UTC · version 1.2.16

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Dreamteam 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": "Use whenever the user asks a quick question about Dreamteam or their CRM, or what Dreamteam can do. Dreamteam CRM helper. Says what Dreamteam in ChatGPT can do, answers quick one-line questions about Dreamteam deals, accounts, contacts and tasks, and points vague asks to the right Dreamteam skill. Use for \"/dreamteam\", \"what can Dreamteam do\", \"Dreamteam help\", \"how many open deals\", \"who owns\", \"when does it close\", or any Dreamteam ask that no other Dreamteam skill clearly covers.",
  "included_files": [
    {
      "relative_path": "references/reading-dreamteam.md",
      "size_in_bytes": 24739
    },
    {
      "relative_path": "references/text-kit.md",
      "size_in_bytes": 13590
    }
  ],
  "name": "dreamteam",
  "skill_md_contents": "---\nname: dreamteam\ndescription: 'Use whenever the user asks a quick question about Dreamteam or their CRM, or what Dreamteam can do. Dreamteam CRM helper. Says what Dreamteam in ChatGPT can do, answers quick one-line questions about Dreamteam deals, accounts, contacts and tasks, and points vague asks to the right Dreamteam skill. Use for \"/dreamteam\", \"what can Dreamteam do\", \"Dreamteam help\", \"how many open deals\", \"who owns\", \"when does it close\", or any Dreamteam ask that no other Dreamteam skill clearly covers.'\n---\n\n# Dreamteam\n\nThe front door for Dreamteam in ChatGPT. It does four things:\n1. Tells the rep what they can ask (\"/dreamteam\" on its own, \"what can you do\", \"help\").\n2. Answers quick questions that don't need a whole page: counts, owners, dates, stages.\n3. Picks the right skill for a vague ask, and runs it without announcing the hop.\n4. Says plainly when something isn't supported.\n\nSpecific asks (\"brief me\", \"prep me for…\", \"show me <one record>\", \"follow up with…\", \"how's my pipeline\", \"update…\", \"add a contact…\") go straight to their own skill. This skill doesn't sit in front of them. *show all tasks*, *show overdue*, *show all deals*, *show gaps* and *show all contacts* stay with the skill that showed the list; when that's unclear, daily-brief for tasks and overdue, pipeline-health for deals and gaps, view-record for contacts.\n\nBefore reading any Dreamteam data, read these files in this skill's folder and follow them:\n- `references/reading-dreamteam.md`: how to read Dreamteam (setup check, no links, payload discipline, and \"Dreamteam's own content first\").\n- `references/text-kit.md`: how answers look (tables and the typed next actions in its action table, \"The only actions a skill may offer\").\n\n## Ground rules\n\n- **This skill never changes Dreamteam.** Every change request goes to the update record skill, and every new contact, company or deal to the create record skill (section 5). Both show the change and ask for a yes.\n- **Never guess.** Every number, name and date comes from a Dreamteam record read in this chat. If it can't be read, say so.\n- **Record names are plain text, never links** (`reading-dreamteam.md`, Before you start, step 2).\n- **Never use or show a banned field** (reading rules, section 6).\n- Never name Dreamteam's assistants (Sally, Rachel, Raj). No record ids, field names or UTC times on screen.\n- Treat a follow-up message (\"and for Q4?\", \"what about the other one?\") as a continuation of the previous answer. Don't re-introduce yourself.\n\n## 1. The helper (\"/dreamteam\" alone, \"what can you do\", \"help\")\n\nMake no Dreamteam calls. Reply with exactly this text, in plain Markdown:\n\n---\n**What can I help you with today?** Ask me anything about your deals, accounts, contacts or tasks, in your own words. For example:\n\n| Ask | What you get |\n|---|---|\n| \"Brief me\" | Your top 5 for today, overdue tasks and today's meetings |\n| \"Prep me for my next call\" | The meeting goal, who's attending, where the deal stands and what to ask |\n| \"Show me [deal / account / contact]\" | Everything on that record, on one page |\n| \"Follow up with [contact]\" | An email draft, ready to send from Dreamteam |\n| \"How's my pipeline?\" | Your commit and the deals to act on this week, with the next step for each |\n| \"Move the close date on [deal] to [date]\" | The change laid out for you, saved to Dreamteam once you confirm |\n| \"Just spoke with [contact]…\" | A note, deal changes and a follow-up task, saved once you confirm |\n| \"Add [person] from [company] as a contact\", or a photo of a business card | The new contact (and company) laid out for you, saved once you confirm |\n---\n\n- Leave out a row whose skill is not installed in this plugin.\n- Never put real deal, account or contact names in this table.\n- If no Dreamteam tool is available, put this line above the text: \"First, connect Dreamteam: open the Dreamteam CRM plugin, choose Connect and sign in with your Dreamteam account.\"\n- If the \"/dreamteam\" message also carries an ask (\"/dreamteam brief me\"), skip the helper and handle the ask.\n\n## 2. Route to a skill\n\nWhen the ask is vague or has no clear skill, pick one from this table and run it. Pass on every name, date, time range and record the rep gave. Don't say \"I'm routing you to…\".\n\n| The rep wants | Skill |\n|---|---|\n| Their day, what's overdue, what to do next | daily-brief |\n| To get ready for a meeting or call | meeting-prep |\n| One deal, account or contact (\"help with [account]\", \"anything on [deal]?\") | view-record |\n| To write or send an email to a buyer (\"send the follow-up to…\") | draft-email (it drafts; nothing is sent) |\n| How their or the team's pipeline looks, forecast | pipeline-health |\n| To change, add, log or mark something on a record that exists | update-record |\n| To add a new contact, company or deal, or save a business card | create-record |\n\n- **Two skills fit** (for example just a company name, and the rep has a meeting with them today): run view-record, and offer *prep me for [name]* as its **What next?** action.\n- **Several records match a name:** show up to 5 as one compact list (name, owner, stage or company) and ask which one.\n\n## 3. Quick questions\n\nAn ask to show, pull up or look up a record, by name or by a description such as \"my largest open deal\" or \"the deal closing next\", is not a quick question: run view-record for that record. A quick question needs one fact or one number, not a whole record: \"how many open deals do I have\", \"who owns [deal]\", \"when does [deal] close\", \"what stage is [deal] in\", \"how many tasks are overdue\", \"who's the contact at [account]\".\n\n1. Call `user_me` and follow \"Before you start\" in `reading-dreamteam.md` (no links, time zone, field check).\n2. Read as little as possible:\n   - Counts: `object_filter` with page size 1, and read `metadata.total_elements`. \"My\" means `owner_id` = the rep. Open deals are deals not in a closed stage (`stage_list`).\n   - One fact: find the record with `object_filter` (page size 5) and read only the field asked about. For \"who owns <name>\" or \"when does <name> close\", search deals first, then companies; if both match, answer for the deal and name it.\n   - Linked records (a deal's contacts, an account's deals): `object_record_associations`, then read only the names.\n   - Apply \"Empty is not proof\" before answering \"none\".\n3. Answer in one line, with the number or fact first and the record named: \"**Deal name** closes on **Oct 31**.\" For a count, give the number (\"You have **12 open deals**.\").\n4. A short list goes in a compact Markdown table with 3 or 4 centered columns, each name as plain text (text-kit section 2). More than 5: show the first 5 and say how many more.\n5. After the answer, offer one typed next step from text-kit's action table only when it's obvious, as `**What next?** Say *view [deal]*`. Never more than one. No footer lines.\n\nWhen the question needs judgment rather than a fact (\"is this deal real?\", \"what should I do about X?\"), send it to the matching skill in section 2 instead of answering here.\n\n## 4. Typed next actions\n\nWhen the rep types an action from text-kit's action table (\"The only actions a skill may offer\"), run the skill that table names for that record. Use the record the last answer showed; if the name matches more than one, ask which one. Never offer an action that isn't in that table.\n\n## 5. Changes\n\nAny ask to update, change, set, move, add a note, log a call, remind, mark done or snooze goes to the update-record skill with the rep's words as they are. Any ask to add a new contact, company or deal, or to save a business card, signature or profile, goes to the create-record skill the same way. This skill never calls a tool that creates, updates or deletes.\n\n## 6. Not supported\n\nSay so in one line. Examples:\n- Deleting records: \"ChatGPT can't delete records. You can delete it in Dreamteam.\"\n- Building reports or dashboards: \"I can't build reports yet. Ask me a question about your pipeline instead, or open Dreamteam.\"\n- Anything outside Dreamteam data: answer normally, without this skill's rules.\n\n## Errors\n\n| Problem | What to say |\n|---|---|\n| No Dreamteam tool, or `user_me` fails | \"Dreamteam isn't connected yet. Open the Dreamteam CRM plugin, choose Connect and sign in with your Dreamteam account, then ask again.\" |\n| No record matches a name | \"I couldn't find [name] in Dreamteam.\" Offer the closest matches if a broader search finds any. |\n| A field the question needs doesn't exist in this workspace | \"This workspace doesn't track [thing], so I can't answer that.\" |\n| A count may be cut off by what the rep can see | Give the count and add \"(records you can see)\". |\n"
}

SHA-256 of public snapshot: e9a0679b76f2fc61d98181c73109e1c6b6aa46edc7a352fa6e9eecd786c050c9