SSO, RBAC & audit · Any model, your keys · No seat tax
The weekly dependency-upgrade runbook: upgrade tiers, the verification gate, breaking-change handling, the ledger, and guardrails.
kortix marketplace install kortix-starter:dependency-upgrade-skill# Read the durable ledger first — last-run state, open PRs, known broken
# upgrades, and pinned packages to skip.
cat memory/dependency-upgrade-log.md 2>/dev/null || echo "(no ledger yet)"
# Check any open upgrade PRs from a prior run.
gh pr list --repo {{target_repo}} --state open \
--search 'in:title "chore(deps)" OR label:dependencies' \
--json number,title,headRefName,statusCheckRollup,url
# Warm clone at /workspace/repo if present; else clone fresh (blobless).
if [ -d /workspace/repo/.git ]; then
cd /workspace/repo && git fetch origin && git checkout main && git reset --hard origin/main
else
git clone --filter=blob:none https://github.com/{{target_repo}}.git /workspace/repo
cd /workspace/repo
fi
# Install so the toolchain can resolve versions.
pnpm install --frozen-lockfile 2>&1 | tail -20
pnpm /
npm / bun / pip / cargo…) to the project's toolchain.cd /workspace/repo
pnpm outdated --recursive --json 2>/dev/null || pnpm outdated --recursive
pnpm audit --json 2>/dev/null | jq '.advisories | length' || true
| Tier | Criteria | Default action |
|---|---|---|
| patch | x.y.Z only | Apply + verify; group into one PR |
| minor | x.Y.z | Apply + verify; group by area or fold into the patch PR |
| major | X.y.z | Apply per package; verify with breaking-change analysis; own PR (or small cohesive group) |
pinned-packages section.cd /workspace/repo
BRANCH="upgrade/deps-$(date +%Y-W%V)"
git checkout -b "$BRANCH" origin/main # or check out an existing branch from this week
cd /workspace/repo
npx taze minor --recursive --write 2>&1 | tee /tmp/taze-minor.log
pnpm install 2>&1 | tee /tmp/install-minor.log
~30 lines of non-trivial code, revert this major, file a tracked issue, and continue with the rest.
cd /workspace/repo
pnpm install 2>&1 | tee /tmp/up-install.log
pnpm typecheck 2>&1 | tee /tmp/up-typecheck.log
pnpm lint 2>&1 | tee /tmp/up-lint.log
pnpm build 2>&1 | tee /tmp/up-build.log
pnpm test 2>&1 | tee /tmp/up-unit.log
pnpm test:integration 2>&1 | tee /tmp/up-integration.log # if < ~10 min
pnpm audit --prod 2>&1 | tee /tmp/up-audit.log
| Failure | Action |
|---|---|
| Type error from an upgraded package's types | Apply the migration (fix inline if 2–3 lines); else revert + file an issue |
| Test failure testing the upgraded package | If behavior legitimately changed, update the test; if it's a regression, revert + file |
| Test failure in an UNRELATED test | File a bug (likely pre-existing flake); don't revert unless you can prove causation |
| Build failure | Fix the import/config; if > 3 non-mechanical files, split the major into its own PR |
| Audit finds a NEW vuln from the upgrade | Revert + file. Never trade a clean audit for a dirty one |
cd /workspace/repo
git add '**/package.json' pnpm-lock.yaml
git add -p # review any migration source changes before staging
git commit -m "chore(deps): upgrade dependencies $(date +%Y-W%V)
Verification: typecheck ✓ lint ✓ build ✓ unit ✓ integration ✓ audit ✓"
cd /workspace/repo
git push origin "$BRANCH"
gh pr create --repo {{target_repo}} --base main --head "$BRANCH" \
--title "chore(deps): upgrade dependencies $(date +%Y-W%V)" \
--label dependencies \
--body "Generated by the dependency upgrade agent. The full suite passed in the
sandbox before this PR was opened. Verification: install/typecheck/lint/build/
unit/integration/audit all ✓. A human owns the merge."
memory/dependency-upgrade-log.md (see
<ledger-format>), then open + self-merge a scoped change request for the ledger
update only.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.