mcpbeat

Hubspot Pipeline Health

openai/hubspot-pipeline-health

Use when reviewing HubSpot pipeline health, forecasts, stale deals, slipping close dates, or open deal risks.

425 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-pipeline-health

What comes with it

247 bytes besides the instruction
agents/openai.yaml

The instruction itself

3 sections, as written by the author

HubSpot Pipeline Health

Turn open deal data into a concise pipeline-health readout. Follow ../hubspot/SKILL.md for access, URLs, pagination, and write approvals.

Workflow

  • Call get_user_details and confirm deal read access.
  • Clarify pipeline, owner/team, timeframe, and closed-deal inclusion. Default to open deals in the current quarter or next 90 days.
  • Discover deal fields: dealname, amount, dealstage, pipeline, closedate, owner, forecast, next step, last activity/contact.
  • Use get_properties for pipeline/stage/forecast enums, then search_crm_objects for open deals. Check total and page or segment large pipelines.
  • Use get_crm_objects for high-signal deals; use associatedWith for companies/contacts only when context changes the recommendation.

Risk And Output

Flag deals with past or near close dates, stale activity, missing owner/contact/next step, missing amount/stage/close date, late stage with weak recent touch, or stage concentration without clear next actions. State which signals were unavailable.

Return coverage, 2-4 executive takeaways, an at-risk deals table with URLs, pipeline hygiene patterns, recommended follow-ups, and caveats. Use manage_crm_objects only after the core confirmation table.

How to use it

Copy the folder

Take openai/hubspot-pipeline-health 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.