← 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":251}]
Compare saved observations
Download comparison JSONFull technical diff · 1 changed fields
changed /included_files
BEFORE
[]
AFTER
[
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 251
}
]Full snapshot data
{
"name": "hubspot-customer-prep",
"description": "Use when preparing HubSpot customer briefs for meetings, renewals, QBRs, sales calls, escalations, handoffs, or follow-ups.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 251
}
],
"skill_md_contents": "---\nname: hubspot-customer-prep\ndescription: Use when preparing HubSpot customer briefs for meetings, renewals, QBRs, sales calls, escalations, handoffs, or follow-ups.\n---\n\n# HubSpot Customer Prep\n\nAssemble a customer-ready brief while separating CRM facts from inferred recommendations. 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 read access to the needed object types.\n2. Clarify seed record and goal: company, contact, deal, ticket, meeting type, attendees, date, and desired outcome.\n3. 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.\n4. 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.\n5. Use `associatedWith` searches for related contacts, companies, deals, and tickets. Fetch selected records with `get_crm_objects` when richer fields are needed.\n\n## Brief\n\nReturn 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`.\n"
}SHA-256: 6a5df5a6e6080702e69d0f9fae7fb5bc5ccaaad01bb12eb3c559da5de4009bc4