SSO, RBAC & audit · Any model, your keys · No seat tax
Runbook for finding accounts due a QBR, pulling usage, health, support, and expansion signals, and assembling the draft deck and briefing doc.
kortix marketplace install kortix-starter:qbr-deck-assembly-skill{{qbr_date_property}} on every account in HubSpot and select those
whose date falls within {{lookahead_days}} days from today. For each
selected account, also pull:{{qbr_date_property}} value at all, skip it and note
the gap in the run summary rather than guessing a cadence.| Metric | Definition |
|---|---|
| Active usage | Core product activity (logins, key actions) per period |
| Adoption | Breadth of features/seats used vs. what's licensed |
| Trend | Direction and magnitude of change quarter over quarter |
{{decks_folder}}, named for the account and the
quarter (e.g. Acme Corp — Q2 2026 QBR). Use this section order:{{decks_folder}}, named to match the deck,
holding the backup detail that doesn't fit on a slide: the full support
ticket list referenced in Step 3, the raw usage numbers behind the trend
chart, the CSM notes verbatim, and the specific data point behind each
expansion signal. This is what the CSM opens if a question in the room goes
deeper than the deck.{{decks_folder}}, plus any
account skipped for missing a QBR date. Do not open, share, or present
anything — that's the CSM's job.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.