SSO, RBAC & audit · Any model, your keys · No seat tax
Renewal-workflow runbook: find renewals 90/60/30 days out, assemble the value/usage/expansion packet, draft outreach, and flag at-risk renewals.
kortix marketplace install kortix-starter:renewal-prep-skillkortix_renewal_stage_alerted property marks the last window surfaced), not
in a local ledger file. A sweep can find several accounts at once; handle each
as an independent unit — a failure preparing one account's packet is logged
and skipped, never blocking any other account in the same sweep.
{{renewal_date_property}} set:GET /crm/v3/objects/deals/search
filterGroups: [
{ propertyName: "{{renewal_date_property}}", operator: "LTE", value: <today + 90d> },
{ propertyName: "dealstage", operator: "NEQ", value: "closedlost" }
]
properties: ["{{renewal_date_property}}", "amount", "dealstage", "hubspot_owner_id",
"kortix_renewal_stage_alerted", "notes_last_updated", "hs_lastmodifieddate"]
kortix_renewal_stage_alerted already equals that bucket — it was
packeted on a prior run. A deal moving into a new, tighter bucket (e.g. 90 →
60) always gets a fresh packet, since more has likely changed.hubspot_owner_id → name). Read prior call and email activity to reconstruct
what's been delivered and discussed since the account signed or last renewed.| Signal | What it means |
|---|---|
| Stage unchanged for an extended period | Deal has stalled |
| Contract value trending down vs. last term | Account may be scaling back |
| No logged activity in a long stretch | Relationship's gone quiet |
| Notes mentioning a competitor, budget freeze, or churn intent | Explicit risk |
kortix_renewal_stage_alerted on each packeted deal to the bucket just
surfaced (with a timestamp). This is the only HubSpot write — never the deal
stage, amount, or pipeline.The role-to-grant policy, extra-scrutiny cases, the approval handshake, and how an applied grant gets logged.
Get a complete picture of any company or person before outreach. This skill always works with web search, and gets significantly better with enrichment and CRM data.
Daily runbook for budget pacing, CPA/ROAS drift, underperformer detection, and anomaly flags across Google Ads and Meta Ads, plus how to rank and word optimization recommendations.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
Extract-and-match runbook for incoming vendor invoices: line-item extraction, PO/prior-invoice matching, duplicate + overcharge detection, and the ledger + approval hand-off.
Search, dedupe against the seen-mentions ledger, classify sentiment and notability, and post a digest with suggested response drafts — the daily brand-monitor runbook.