mcpbeat

Hubspot Customer Prep

openai/hubspot-customer-prep

Use when preparing HubSpot customer briefs for meetings, renewals, QBRs, sales calls, escalations, handoffs, or follow-ups.

417 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
4915
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/openai/plugins --skill hubspot-customer-prep

What comes with it

251 bytes besides the instruction
agents/openai.yaml

The instruction itself

3 sections, as written by the author

HubSpot Customer Prep

Assemble a customer-ready brief while separating CRM facts from inferred recommendations. Follow ../hubspot/SKILL.md for access, URLs, pagination, and write approvals.

Workflow

  • Call get_user_details and confirm read access to the needed object types.
  • Clarify seed record and goal: company, contact, deal, ticket, meeting type, attendees, date, and desired outcome.
  • Find the seed record with search_crm_objects using name, domain, email, deal name, or ticket subject. If multiple records match, return a disambiguation list with URLs.
  • Discover properties with search_properties: company owner/lifecycle/domain; contact title/email/last contact; deal amount/stage/close date/next step; ticket status/priority/category.
  • Use associatedWith searches for related contacts, companies, deals, and tickets. Fetch selected records with get_crm_objects when richer fields are needed.

Brief

Return source record URLs, snapshot, people, open opportunities, support health, recommended agenda, questions to ask, follow-ups, and caveats. For tasks, next steps, associations, ownership, or stage changes, show exact proposed changes and get approval before manage_crm_objects.

How to use it

Copy the folder

Take openai/hubspot-customer-prep from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.