← HubSpotCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
changed
Update to HubSpot
Snapshot Sep 30, 2026 · 23:18 UTC · version 6.0.0
Collection source: not recorded for this historical snapshot. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.
Supporting file metadata differs
Newly listed paths: agents/openai.yaml. This compares saved file lists, not package contents; a different collection source can change the list.
Observed in package metadata. These changes alone do not establish a new customer-facing feature.
Supporting files
Before
[]
After
[{"relative_path":"agents/openai.yaml","size_in_bytes":247}]
Compare saved observations
Download comparison JSONFull technical diff · 1 changed fields
changed /included_files
BEFORE
[]
AFTER
[
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 247
}
]Full snapshot data
{
"name": "hubspot-pipeline-health",
"description": "Use when reviewing HubSpot pipeline health, forecasts, stale deals, slipping close dates, or open deal risks.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 247
}
],
"skill_md_contents": "---\nname: hubspot-pipeline-health\ndescription: Use when reviewing HubSpot pipeline health, forecasts, stale deals, slipping close dates, or open deal risks.\n---\n\n# HubSpot Pipeline Health\n\nTurn open deal data into a concise pipeline-health readout. Follow [../hubspot/SKILL.md](../hubspot/SKILL.md) for access, URLs, pagination, and write approvals.\n\n## Workflow\n\n1. Call `get_user_details` and confirm deal read access.\n2. Clarify pipeline, owner/team, timeframe, and closed-deal inclusion. Default to open deals in the current quarter or next 90 days.\n3. Discover deal fields: `dealname`, `amount`, `dealstage`, `pipeline`, `closedate`, owner, forecast, next step, last activity/contact.\n4. Use `get_properties` for pipeline/stage/forecast enums, then `search_crm_objects` for open deals. Check `total` and page or segment large pipelines.\n5. Use `get_crm_objects` for high-signal deals; use `associatedWith` for companies/contacts only when context changes the recommendation.\n\n## Risk And Output\n\nFlag 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.\n\nReturn 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.\n"
}SHA-256: 75c5761a19b675bc0bcbcaf50eea9030a8c324c26f48b5f6b164e58da797ce1c