Skip to content
cccskills
FreePublished on GitHub

pipeline-hygiene-rules

Check open HubSpot deals for inactivity, missing next steps or close dates, stalled stages, and overdue tasks. Update an internal flag, send grouped Slack reminders to each representative, and report the highest priority deals to the sales manager.

OriginalShow the original description

Daily HubSpot pipeline-hygiene rules — staleness, missing next step/close date, stage stalls, and overdue tasks — plus how to nudge the owning rep in Slack and escalate the day's worst offenders to the sales manager. The only write is an internal hygiene flag; stage, owner, and amount are never touched.

Works withSlackHubSpot
See how to install

Good for

  • Finding deals with no recent activity
  • Checking for missing next steps and close dates
  • Reminding representatives about overdue tasks
  • Reporting priority deal issues to the sales manager

Files included (1)

  • SKILL.md4.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

<skill name="pipeline-hygiene-rules"> <overview> Turn four hygiene checks into a same-day nudge instead of a finding buried in next week's pipeline review. A daily cron spawns a fresh session with read-mostly access to HubSpot; this skill pulls every open deal, scores it against the four rules, nudges the owning rep in Slack, and escalates the day's worst offenders to the sales manager. Every run recomputes from HubSpot's current state — there is no carryover between days. </overview> <when-to-load> - The daily cron fires the pipeline-hygiene scan. - A human asks the agent to check pipeline hygiene or explain why a specific deal was flagged. </when-to-load> <workflow>

Step 1 — Pull every open deal (read-only)

Pull all open deals: current stage, amount, close date, next step field, and how long the deal has sat in its current stage (time-in-stage). Read-only — no field on the deal is changed in this step.

Step 2 — Pull activities per deal (read-only)

Pull logged calls, emails, meetings, and notes per deal, with timestamps. This is the basis for the staleness check in Step 4.

Step 3 — Pull tasks per deal (read-only)

Pull open tasks tied to each deal, with due dates. A task past its due date with no completion is overdue.

Step 4 — Apply the four hygiene rules

Evaluate every open deal against all four independently — a deal can trip more than one:

RuleTrip condition
StaleNo logged activity (call, email, meeting, note) in the last {{stale_days}} days
IncompleteMissing next step, missing close date, or both
StalledNo stage change in the last {{stall_days}} days
Overdue taskAt least one open task past its due date

Step 5 — Write the hygiene flag (the only write)

For every deal that trips at least one rule, write the internal hygiene-flag field on the deal noting which rule(s) tripped and the date. This is the only field the agent ever writes — never the stage, the owner, or the amount. Deals that trip no rule get their flag cleared if previously set.

Step 6 — Nudge the owning rep in Slack

For each flagged deal, send the owning rep a Slack nudge naming the deal, which rule(s) tripped, and the concrete action needed:

Rule trippedNudge action
StaleLog the last touchpoint or make contact today
IncompleteSet the missing next step and/or close date
StalledMove the deal forward or note why it hasn't
Overdue taskComplete or reschedule the task

Group multiple flagged deals for the same rep into one message rather than one message per deal.

Step 7 — Escalate the day's worst to {{escalation_channel}}

After all rep nudges are sent, rank flagged deals by:

  1. Number of rules tripped at once (most rules first).
  2. Deal amount at risk (largest first, as a tiebreaker).
  3. Days since last activity (longest first, as a second tiebreaker).

Post the top offenders to {{escalation_channel}} in one message: deal name, owning rep, amount, which rules tripped, and days since last activity. Post exactly once per run.

</workflow> <guardrails> - **Read-mostly.** Deals, stage history, activities, and tasks are read-only. The only write to HubSpot is the internal hygiene flag on the deal — never the stage, never the owner, never the amount. - **No memory between runs.** Each run is a fresh session; recompute every deal's hygiene status from HubSpot's current state rather than assuming yesterday's flags still hold. - **Nudge and flag only.** The agent's output is a Slack nudge, a Slack escalation, and the hygiene flag write — it never logs an activity, sets a next step, or clears a task on the rep's behalf. - **Scoped secrets.** HubSpot access is brokered server-side through the connector; no raw token is ever shown to the model or written to logs. - **People decide, not the agent.** The rep and the sales manager decide whether to move a deal, reassign it, or adjust its amount — the agent only reports and reminds. </guardrails> </skill>

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

access-policy

FreeSummary

Review Slack access requests against Okta role and team information, then prepare narrowly scoped GitHub or AWS IAM permissions. Apply changes only after an eligible person's approval and record the grant, reasoning, approver, and timestamp.

  • Reviewing GitHub repository access requests from Slack
  • Preparing AWS IAM permissions for a specific task
  • Routing sensitive access requests for additional review
kortix-ai/suna20.3KUpdated Oct 22, 2026

account-research

FreeSummary

Research companies and people before outreach or meetings. Combines business profiles, recent news, hiring signals, and key contacts into a sourced brief with talking points and suggested questions, adding relationship history when CRM data is connected.

  • Research a prospective customer before outreach
  • Prepare background information for meeting attendees
  • Compare a competitor's products and positioning
kortix-ai/suna20.3KUpdated Oct 22, 2026

Review daily Google Ads and Meta Ads results for budget pacing, declining performance, and unusual activity. Get prioritized findings with supporting numbers and concrete recommendations for a marketing team to assess and carry out.

  • Checking whether campaign budgets are being spent on schedule
  • Investigating rising acquisition costs or falling ad returns
  • Finding ads and keywords that spend without converting
kortix-ai/suna20.3KUpdated Oct 22, 2026

agent-browser

FreeSummary

Automate website tasks such as navigating pages, filling forms, clicking buttons, taking screenshots, and extracting data. The skill also supports web app testing, with specialized guides for Electron desktop apps, Slack, and cloud browsers.

  • Automate form entry and page navigation
  • Capture screenshots and extract page data
  • Explore web apps for bugs
kortix-ai/suna20.3KUpdated Oct 22, 2026

ap-invoice-match

FreeSummary

Process emailed vendor invoices by extracting details, comparing them with purchase orders and invoice history, and recording duplicates, overcharges, or missing orders. Summarize results in Slack for human review; payment approval and execution remain with people.

  • Checking incoming invoices against purchase orders
  • Finding duplicate invoices and likely resends
  • Reviewing unit prices and remaining order balances
kortix-ai/suna20.3KUpdated Oct 22, 2026

billing

FreeSummary

Guide changes to Kortix billing code, admin controls, and pricing screens. Explain how plans, trials, enterprise contracts, and access exceptions should work, where pricing is defined, and which audited routes must handle account changes.

  • Update billing logic and its specification together
  • Review how trials and enterprise contracts are handled
  • Find the code that defines prices and allowances
kortix-ai/suna20.3KUpdated Oct 22, 2026

See all skills by kortix-ai

Report a problem with this skill