Ops

This skill should be used when tracking API spend, analyzing billing data, monitoring service costs, running budget reports, or optimizing agent spend across Anthropic, Vercel, Railway, and other platforms. Invoke when asked about "cost tracking", "billing analysis", "spend report", "API costs", "usage monitoring", "budget vs actual", "cost optimization", or "which agents cost the most".

This skill should be used when the user asks to "check deployment health", "verify service connectivity", "validate environment variables before deploy", "run a pre-deploy smoke check", or "diagnose a Vercel, Railway, Redis, or Postgres connection issue". Runs deterministic shell scripts for infrastructure health checks and environment validation, returning structured JSON instead of burning context on inline bash logic.

This skill should be used when the user wants to publish a package to npm, bump a version, release a new version, or mentions "npm publish", "bun publish", "version bump", or "release to npm". Handles version bumping, changelog updates, default-branch release delivery, scripted npm web login and bun publish confirmation (--local opens a browser, --remote prints a link). Do not trigger for unrelated uses of "release" (e.g. GitHub releases, press releases).

This skill should be used when the user asks to "integrate Plaid", "connect a bank account", "sync bank transactions", "add Plaid Link to my app", or "implement financial data access". Integrates the Plaid API for bank account connections and transaction syncing in TypeScript/Bun applications.

Finds stale and resource-hungry processes, scores them by waste, and presents a cleanup report with friendly names. Use this skill when the user says 'what's eating my RAM', 'kill stale processes', 'clean up my machine', 'free up memory', 'my computer is slow', 'what's running', 'too many things open', or asks to find/kill background processes. Also use proactively when you notice sluggishness, process spawn failures, or many duplicate processes during normal work.

Wait for CI/CD pipelines to finish after a push, then act on the result. Use after git push or opening a PR, and for "wait for CI", "check if the build passes", "monitor the pipeline", "is CI green?", or any push-then-verify cycle that must block on results. Supports GitHub Actions, GitLab CI, and Vercel deployments.