Profile My skills Saved My plugins Edit profile Submit a skill

Use Available Integrations

Discovers session platform integrations, inspects existing state, and acts only on the delta — falling back to direct API or CLI when tools lack an operation. Use when deploying, provisioning, or managing Vercel, GitHub, Railway, Neon, or other external platform resources.

jcdavis131 Updated
Integrations & APIs

File contents

Use Available Integrations

Discover what's available, load tools, inspect state, act on the delta only.

The move

  1. Discover — what platform integrations/tools the session exposes.
  2. Load tools — don't call raw API when a loaded tool covers the op.
  3. Inspect state — existing projects, deploy status, repos (ground truth).
  4. Act on delta — create/deploy only what's missing; don't redeploy green projects.
  5. Fallback — direct authenticated API for ops tools don't expose; reuse same credential.

Why delta-only

Redeploying green projects wastes work and risk. "Two missing projects" is the actual work.

Extended patterns

Credentials, monorepo deploy gotchas, prod architecture, fallback order: reference.md

Anti-patterns

Assuming nothing deployed; asking for token when stored; raw API when tool exists; acting without inspecting state.

Pair with

  • session-orient · affected-tests · respect-the-guard · correct-assumptions

jcdavis131/cursor-agent-skills/tree/main/skills/use-available-integrations commit f9e98e147e

Browse category

Frequently asked questions

npx skillmds@latest add jcdavis131/use-available-integrations