SSO, RBAC & audit · Any model, your keys · No seat tax
Breaks down closed deals by segment, competitor, price, and stage of death, clusters close reasons into themes, and posts themes plus recommendations to Slack.
kortix marketplace install kortix-starter:win-loss-patterns-skillhubspot connector, read-only, pull every deal whose stage is
closed-won or closed-lost, with: close date, amount, segment/plan (or
company size if no segment field), the deal's stage-history,
{{close_reason_property}}, and {{competitor_property}}.won / (won + lost)). Compare total won amount to total lost amount (deal
value at risk, not just deal count).{{competitor_property}}, group losses (and wins where a competitor was
named and we still won) by named competitor. For each competitor with enough
volume to matter, report the loss count and, where the close reason
mentions it, the reason we lost to them specifically (price, feature gap,
relationship, timing). Deals with no competitor recorded go in an
"unrecorded / no competitor" bucket — don't force a competitor name that
isn't there.{{close_reason_property}} across all closed-lost deals in the window
and group by what the rep meant, not exact wording — e.g. "lost on price,"
"missing feature," "competitor chosen," "champion left / no decision,"
"bad timing." For each theme, note the count and one representative
verbatim reason. If a reason field is blank, count it under "reason not
recorded" rather than guessing.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.