Update to FastAPI Cloud

{
  "description": "Connect and manage databases and third-party resources for FastAPI Cloud apps. Use when the user asks to connect or add a database, Postgres provider, Redis cache, observability service, or other managed service; inspect available integration providers; connect Neon, Redis Cloud, Supabase, or Logfire; list or inspect connected resources; review managed environment variables; or disconnect a resource from an app.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 237
    }
  ],
  "name": "fastapicloud-integrations",
  "skill_md_contents": "---\nname: fastapicloud-integrations\ndescription: \"Connect and manage databases and third-party resources for FastAPI Cloud apps. Use when the user asks to connect or add a database, Postgres provider, Redis cache, observability service, or other managed service; inspect available integration providers; connect Neon, Redis Cloud, Supabase, or Logfire; list or inspect connected resources; review managed environment variables; or disconnect a resource from an app.\"\n---\n\n# FastAPI Cloud Integrations\n\n## Overview\n\nInspect available providers and manage resources connected to a FastAPI Cloud app. Current providers include Neon, Redis Cloud, Supabase, and Logfire; use the CLI provider list as the source of truth for availability.\n\nTreat the connected resource as the integration abstraction. Current integrations configure the app through managed environment variables, but do not define integrations as env-var management alone: future providers may add other behavior and metadata. Follow the current CLI response rather than assuming environment variables are the complete integration contract.\n\n## CLI Baseline\n\nStart with the command needed for the task:\n\n```bash\nuv run fastapi cloud integrations --help\n```\n\nOnly check the CLI version after the command is missing or reports an incompatible command surface:\n\n```bash\nuv run fastapi cloud --version\nuv run fastapi cloud integrations --help\n```\n\nIntegration commands require FastAPI Cloud CLI `0.24.0` or newer. If the project CLI is older, ask before updating the existing project environment:\n\n```bash\nuv add -U \"fastapi[standard]\"\nuv lock --upgrade-package fastapi --upgrade-package fastapi-cloud-cli\n```\n\nInstall or update `fastapi[standard]`, not `fastapi-cli` directly. The standard FastAPI extra provides the `fastapi` command and FastAPI Cloud CLI integration.\n\n## JSON Output\n\nUse `--json` whenever the command supports it. JSON mode is non-interactive: resolve required team, app, and resource IDs before running a mutating command.\n\n## Resolve The Target\n\nPrefer the narrowest available scope:\n\n1. Use an explicit team, app, or resource ID supplied by the user.\n2. Use the app linked to the current directory when it is the intended target.\n3. Read teams, apps, providers, or connected resources only as needed to resolve a missing ID.\n\nUseful read commands:\n\n```bash\nuv run fastapi cloud apps get --json\nuv run fastapi cloud teams list --json\nuv run fastapi cloud apps list --team-id TEAM_ID --json\n```\n\nDo not create or link an app, deploy code, or change environment variables merely to answer an integration query.\n\n## Database And Service Requests\n\nWhen the user asks to connect a database or another external service, check FastAPI Cloud integrations before proposing manual credentials or environment variables:\n\n1. Resolve the intended FastAPI Cloud app and team.\n2. List integration providers for that team.\n3. Match the requested capability to providers reported as available or connected.\n4. If multiple providers fit a generic request such as PostgreSQL, show the supported choices and ask which one the user wants.\n5. Use the resource connection flow when a supported provider is selected.\n6. If no integration supports the request, explain that clearly before offering manual environment-variable configuration.\n\nDo not assume a service is unsupported from the static provider examples in this skill. Always use `integrations providers list` when the CLI is available. Do not manually set provider credentials when a supported managed integration is appropriate unless the user explicitly prefers manual configuration.\n\n## Providers\n\nList providers and their connection status for the linked app's team:\n\n```bash\nuv run fastapi cloud integrations providers list --json\n```\n\nUse an explicit team when the current directory is not linked or the user selected another team:\n\n```bash\nuv run fastapi cloud integrations providers list --team-id TEAM_ID --json\n```\n\nTreat provider status from this response as authoritative. A provider can be available, connected, or coming soon.\n\n## Connected Resources\n\nList resources connected to the linked app or a specific app:\n\n```bash\nuv run fastapi cloud integrations resources list --json\nuv run fastapi cloud integrations resources list --app-id APP_ID --json\n```\n\nInspect one resource after resolving its ID from the list:\n\n```bash\nuv run fastapi cloud integrations resources get RESOURCE_ID --json\nuv run fastapi cloud integrations resources get RESOURCE_ID --app-id APP_ID --json\n```\n\nThe resource details include provider metadata, a provider console URL, and managed environment variable names. Do not claim the CLI reveals environment variable values.\n\n## Connect A Resource\n\nConnecting a provider resource is completed in the FastAPI Cloud dashboard. In JSON mode, the CLI does not open a browser; it returns a `connect_url` to surface to the user:\n\n```bash\nuv run fastapi cloud integrations resources connect --json\nuv run fastapi cloud integrations resources connect --app-id APP_ID --json\n```\n\nDo not claim the connection is complete merely because the URL was generated. Let the user finish provider selection and authorization in the browser, then verify with:\n\n```bash\nuv run fastapi cloud integrations resources list --app-id APP_ID --json\n```\n\n## Disconnect A Resource\n\nRead the resource first and explain the effect before disconnecting it. Disconnecting removes the resource's managed environment variables from the FastAPI Cloud app, but does not delete the resource from Neon, Redis Cloud, Supabase, or Logfire.\n\nOnly disconnect when the user explicitly asks. JSON mode requires both the resource ID and confirmation:\n\n```bash\nuv run fastapi cloud integrations resources get RESOURCE_ID --app-id APP_ID --json\nuv run fastapi cloud integrations resources disconnect RESOURCE_ID --app-id APP_ID --yes --json\n```\n\nReport the disconnected resource ID and any managed environment variable names removed from the app. Never substitute a similarly named resource without confirming its ID.\n\n## Authentication\n\nIf a read command returns `not_logged_in` or `invalid_token`, stop and report the blocker. Ask before starting login. After approval, use the JSON device flow:\n\n```bash\nuv run fastapi cloud auth login --no-open --json\nuv run fastapi cloud auth wait --device-code DEVICE_CODE --interval 5 --timeout 300 --json\n```\n\nSurface only the verification URL and user code needed for authorization. Never print or request token values.\n"
}