Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/hubspot-deal-pipeline-automation
Automate and audit HubSpot deal pipeline operations without destroying real pipeline — covering stage automation loops, stale-deal safe-close logic, forecast reconciliation, custom property drift detection, quota dashboard cache-busting, and multi-pipeline duplicate detection.
Passed 17 of 22 test cases with the skill, and 6 of 22 without it.
and 14 more in the full report
11 fixed6 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our RevOps team suspects deal #98765 is stuck bouncing between stages. Provide a curl and jq command line snippet to inspect the historical stage transitions for this specific deal to detect oscillation.
| Checked | Without skill | With skill |
|---|---|---|
| Queries the deal changelog endpoint /crm/v3/objects/deals/98765/changelog. | Missed | Passed |
| Filters output using jq for changelog entries where propertyName equals dealstage. | Missed | Passed |
The instructions your model reads when the skill loads.
Automate HubSpot deal pipelines without blowing up real revenue. This is not a walkthrough of workflow builder UI — it is the engineering behind six failure modes that silently destroy RevOps data while every dashboard stays green until a rep's quota call reveals the damage.
The six production failures this skill prevents:
Stage automation loops — a workflow moves a deal to "Demo Scheduled", which triggers a second workflow enrolled on "Demo Scheduled" that moves it back to "Qualified", which triggers the first workflow again. The deal bounces between stages until HubSpot's 100-action daily workflow execution limit for that deal is exhausted. RevOps sees "workflow failure" alerts but no stage history that makes sense.
Stale-deal auto-closing — a cleanup workflow auto-closes deals older than 90 days to clear pipeline bloat. The contact associated with deal #4872 responded to an email this morning. The deal is closed as Lost. The rep calls the contact, who says "I just told someone we were ready to sign." This failure costs quota attainment, not just data quality.
Forecast query inconsistency — amount, hs_projected_amount, and a
custom arr_value property all exist on the same deal. The CRO dashboard
queries amount. The ops team queries hs_projected_amount. RevOps built a
custom rollup on arr_value. At end of quarter they produce three different
forecast numbers for the same deal set with no canonical answer.
Custom property reporting gap — a RevOps engineer renames
deal_source_detail to original_lead_source in the property settings.
Every deal-source dashboard built on the old property name silently returns
zero. No error is thrown. The board sees a 100% collapse in deal source
tracking that is entirely an artifact, not a pipeline signal.
Quota dashboard staleness — HubSpot's reporting layer caches deal stage aggregates. A deal closes at 4:47pm. The quota attainment dashboard doesn't reflect it until 8:30pm. A rep who hit quota at EOD is told they're 3% short. This is a 4-hour cache lag in the default reporting stack, and it
test cases passed, vs 6 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.