SSO, RBAC & audit · Any model, your keys · No seat tax
Classifies open PRs as overdue for review, stale, or carrying unaddressed requested changes, and writes the nudge for whoever owns the next move.
kortix marketplace install kortix-starter:pr-review-sla-skill# List every open PR across the configured repos.
gh pr list --repo {{target_repos}} --state open \
--json number,title,url,author,createdAt,updatedAt,reviewRequests,reviews,comments,commits
{{target_repos}} names more than one.gh pr view --repo {{target_repos}} <PR_NUMBER> \
--json number,title,url,author,createdAt,updatedAt,reviewRequests,reviews,comments,commits
reviews gives each review's state (APPROVED, CHANGES_REQUESTED,
COMMENTED) and timestamp; commits and comments give the last activity;
reviewRequests gives who's currently asked to review.reviewRequests entry and no APPROVED or
CHANGES_REQUESTED review from that reviewer since the request:hours_waiting = now - max(createdAt, last review-request timestamp)
hours_waiting > {{review_sla_hours}}. Nudge target: the requested
reviewer(s).days_idle = now - max(last_commit, last_comment, last_review)
days_idle > {{stale_days}}. Nudge target: the author. A PR already
flagged in Step 2 can also be flagged here if it independently qualifies — the
two checks are separate signals, not mutually exclusive.CHANGES_REQUESTED, check whether the
author has pushed a commit or posted a comment since that review's timestamp.
If not, flag it. Nudge target: the author.| Check | Passes (no nudge) | Fails (nudge) |
|---|---|---|
| Overdue review | Reviewer submitted within SLA | No review after {{review_sla_hours}}h |
| Stale | Any activity within the window | No activity for {{stale_days}}d |
| Unaddressed changes | Author pushed/replied after the review | Silence since CHANGES_REQUESTED |
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.