hubspot

$npx mdskill add openai/plugins/hubspot

Manage and analyze HubSpot CRM records with precision and clarity

  • Solve tasks like searching, creating, updating, or associating CRM records
  • Relies on HubSpot's CRM API for object and property operations
  • Follows strict rules to confirm writes and ensure accurate data handling
  • Returns actionable results with HubSpot links and clear summaries

SKILL.md

.github/skills/hubspotView on GitHub ↗
---
name: hubspot
description: Use when working with HubSpot CRM records to search, summarize, create, update, associate, or analyze objects and properties.
---

# HubSpot

## Rules

1. Call `get_user_details` first; check object read/write availability.
2. Clarify scope: object type, owner/team, pipeline, timeframe, stage, and whether writes are requested.
3. Use `search_properties` for fields, max 5 `keywords`; use `get_properties` for enum values.
4. Use `search_crm_objects` for records, counts, filters, pagination, and associations; use `get_crm_objects` for known IDs. Do not use deprecated `search` or `fetch`.
5. Include clickable HubSpot URLs with UTM params for returned records. State filters, totals, pagination, and whether analysis is sampled.

## Writes

Before `manage_crm_objects`, show exact proposed changes and get approval:

| Object Type | ID | Property | Current Value | New Value |
|---|---:|---|---|---|

On the first confirmation, add: `Want to skip confirmations for this chat? Just ask.`

Batch at most 10 objects. Confirm associations explicitly. Do not write inferred data or overwrite user-entered context without clear consent.

More from openai/plugins

SkillDescription
accessibility-and-inclusive-visualizationMake data visualizations accessible and inclusive. Use when the user needs chart or diagram accessibility guidance, text alternatives for complex visuals, color and contrast review, keyboard support, reduced-motion behavior for animation or parallax, or an accessibility QA workflow for exported figures, UML-like diagrams, and dashboards.
agent-browserBrowser automation CLI for AI agents. Use when the user needs to interact with websites, verify dev server output, test web apps, navigate pages, fill forms, click buttons, take screenshots, extract data, or automate any browser task. Also triggers when a dev server starts so you can verify it visually.
agent-browser-verifyAutomated browser verification for dev servers. Triggers when a dev server starts to run a visual gut-check with agent-browser — verifies the page loads, checks for console errors, validates key UI elements, and reports pass/fail before continuing.
agents-sdkBuild AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, or chat applications. Covers Agent class, state management, callable RPC, Workflows integration, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
ai-elementsAI Elements component library guidance — pre-built React components for AI interfaces built on shadcn/ui. Use when building chat UIs, message displays, tool call rendering, streaming responses, reasoning panels, or any AI-native interface with the AI SDK.
ai-gatewayVercel AI Gateway expert guidance. Use when configuring model routing, provider failover, cost tracking, or managing multiple AI providers through a unified API.
ai-generation-persistenceAI generation persistence patterns — unique IDs, addressable URLs, database storage, and cost tracking for every LLM generation
ai-sdkVercel AI SDK expert guidance. Use when building AI-powered features — chat interfaces, text generation, structured output, tool calling, agents, MCP integration, streaming, embeddings, reranking, image generation, or working with any LLM provider.
aiq-deploy|
aiq-research|