SSO, RBAC & audit · Any model, your keys · No seat tax
Hourly warehouse freshness, row-count, schema-drift, and failed-load checks that alert Slack and draft a GitHub issue with the likely cause.
kortix marketplace install kortix-starter:pipeline-health-check-skillSELECT table_name
FROM information_schema.tables
WHERE table_schema = '{{warehouse_schema}}'
AND table_type = 'BASE TABLE'
ORDER BY table_name;
updated_at, loaded_at,
created_at, or whatever the table's load convention is):SELECT MAX(<timestamp_column>) AS last_loaded
FROM {{warehouse_schema}}.<table>;
last_loaded against the table's SLA: a specific one noted in skill
memory if it has one, else the {{freshness_sla_hours}}-hour default. A table
older than its SLA is a freshness anomaly — likely cause: the upstream load
job stopped running, is silently erroring, or was disabled.SELECT date_trunc('day', <timestamp_column>) AS day, COUNT(*) AS row_count
FROM {{warehouse_schema}}.<table>
WHERE <timestamp_column> >= now() - interval '14 days'
GROUP BY 1
ORDER BY 1;
| Pattern | Likely cause |
|---|---|
| Count far below trend, or zero new rows since last load | Load ran short, silently skipped a batch, or didn't run |
| Count far above trend (e.g. multi-x jump) | Duplicate load, retried job double-inserted, or a batch wasn't deduplicated |
| Count in line with trend | No anomaly |
SELECT column_name, data_type, is_nullable
FROM information_schema.columns
WHERE table_schema = '{{warehouse_schema}}' AND table_name = '<table>'
ORDER BY ordinal_position;
etl_runs,
load_history, a dbt run_results equivalent):SELECT job_name, status, started_at, finished_at, error_message
FROM {{warehouse_schema}}.<load_log_table>
WHERE started_at >= now() - interval '2 hours'
ORDER BY started_at DESC;
error_message verbatim as evidence.gh issue create --repo {{incident_repo}} \
--title "[pipeline-health] <table>: <anomaly type>" \
--body "Detected by the hourly pipeline-health sweep.
**Table:** {{warehouse_schema}}.<table>
**Anomaly:** <freshness | row-count | schema-drift | failed-load>
**Evidence:** <the timestamp / counts / diff / error message>
**Likely cause:** <cause from Step 2-5>
This is a draft for triage — no data, schema, or pipeline change has been made."
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.