SSO, RBAC & audit · Any model, your keys · No seat tax
Our standard positions on liability, indemnification, termination, and the rest, plus how to summarize, flag, and draft a redline.
kortix marketplace install kortix-starter:contract-playbook-skill# List files in the contracts folder, newest first.
drive.files.list(folder={{contracts_folder}}, orderBy="createdTime desc")
# Search {{legal_channel}} for a prior summary post referencing each file name.
# A file with a matching post is already handled — skip it.
slack.search(channel={{legal_channel}}, query=file.name)
docs.documents.get) to pull its actual body, not a Drive preview or the
first page. Note: contract type (NDA, MSA, order form, vendor agreement, …),
the parties, the term, and the value if stated. This becomes the top of the
summary.| Clause | Routine | Flag |
|---|---|---|
| Liability cap | Capped at 12 months' fees | Uncapped, or capped above 12 months' fees |
| Indemnification | Mutual, capped | Unilateral (only us), or uncapped |
| Termination for convenience | Either party, ≤ 90 days notice | Missing, or > 90 days notice |
| Auto-renewal | Opt-in, or opt-out with ≥ 30 days notice | Silent renewal with < 30 days notice |
| Governing law / venue | Our home jurisdiction | Counterparty's jurisdiction or a neutral third one we haven't used before |
| Payment terms | Net 30–45 | Net 60 or longer |
| IP assignment | Foreground IP only | Assigns our background IP or pre-existing tools |
| Confidentiality duration | 3–5 years post-termination | Perpetual, or silent on duration |
docs.documents.batchUpdate
with the request's writeControl/suggester identity set so the change lands as
a suggestion, not an applied edit) — never as a direct write to the document.
Keep the redline close to our standard position (e.g., propose the 12-month cap,
not a negotiating opener). One redline per flagged clause; reference the section
number.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.