{"kind":"Skill","metadata":{"namespace":"community","name":"arize-ai-provider-integration","version":"0.1.0"},"spec":{"description":"Creates, reads, updates, and deletes Arize AI integrations that store LLM provider credentials used by evaluators and other Arize features. Supports any LLM provider (e.g. OpenAI, Anthropic, Azure OpenAI, AWS Bedrock, Vertex AI, Gemini, NVIDIA NIM). Use when the user mentions AI integration, LLM provider credentials, create integration, list integrations, update credentials, delete integration, or connecting an LLM provider to Arize.","files":{"SKILL.md":"---\nname: arize-ai-provider-integration\ndescription: Creates, reads, updates, and deletes Arize AI integrations that store LLM provider credentials used by evaluators and other Arize features. Supports any LLM provider (e.g. OpenAI, Anthropic, Azure OpenAI, AWS Bedrock, Vertex AI, Gemini, NVIDIA NIM). Use when the user mentions AI integration, LLM provider credentials, create integration, list integrations, update credentials, delete integration, or connecting an LLM provider to Arize.\nmetadata:\n  author: arize\n  version: \"1.0\"\ncompatibility: Requires the ax CLI and a configured Arize profile.\n---\n\n# Arize AI Integration Skill\n\n\u003e **`SPACE`** — Most `--space` flags and the `ARIZE_SPACE` env var accept a space **name** (e.g., `my-workspace`) or a base64 space **ID** (e.g., `U3BhY2U6...`). Find yours with `ax spaces list`.\n\u003e **Note:** `ai-integrations create` does **not** accept `--space` — AI integrations are account-scoped. Use `--space` only with `list`, `get`, `update`, and `delete`.\n\n## Concepts\n\n- **AI Integration** = stored LLM provider credentials registered in Arize; used by evaluators to call a judge model and by other Arize features that need to invoke an LLM on your behalf\n- **Provider** = the LLM service backing the integration (e.g., `openAI`, `anthropic`, `awsBedrock`)\n- **Integration ID** = a base64-encoded global identifier for an integration (e.g., `TGxtSW50ZWdyYXRpb246MTI6YUJjRA==`); required for evaluator creation and other downstream operations\n- **Scoping** = visibility rules controlling which spaces or users can use an integration\n- **Auth type** = how Arize authenticates with the provider: `default` (provider API key), `proxy_with_headers` (proxy via custom headers), or `bearer_token` (bearer token auth)\n\n## Prerequisites\n\nProceed directly with the task — run the `ax` command you need. Do NOT check versions, env vars, or profiles upfront.\n\nIf an `ax` command fails, troubleshoot based on the error:\n- `command not found` or version error → see references/ax-setup.md\n- `401 Unauthorized` / missing API key → run `ax profiles show` to inspect the current profile. If the profile is missing or the API key is wrong, follow references/ax-profiles.md to create/update it. If the user doesn't have their key, direct them to https://app.arize.com/admin \u003e API Keys\n- Space unknown → run `ax spaces list` to pick by name, or ask the user\n- LLM provider call fails (missing OPENAI_API_KEY / ANTHROPIC_API_KEY) → run `ax ai-integrations list --space SPACE` to check for platform-managed credentials. If none exist, ask the user to provide the key or create an integration via the **arize-ai-provider-integration** skill\n- **Security:** Never read `.env` files or search the filesystem for credentials. Use `ax profiles` for Arize credentials and `ax ai-integrations` for LLM provider keys. If credentials are not available through these channels, ask the user.\n\n---\n\n## List AI Integrations\n\nList all integrations accessible in a space:\n\n```bash\nax ai-integrations list --space SPACE\n```\n\nFilter by name (case-insensitive substring match):\n\n```bash\nax ai-integrations list --space SPACE --name \"openai\"\n```\n\nPaginate large result sets:\n\n```bash\n# Get first page\nax ai-integrations list --space SPACE --limit 20 -o json\n\n# Get next page using cursor from previous response\nax ai-integrations list --space SPACE --limit 20 --cursor CURSOR_TOKEN -o json\n```\n\n**Key flags:**\n\n| Flag | Description |\n|------|-------------|\n| `--space` | Space name or ID to filter integrations |\n| `--name` | Case-insensitive substring filter on integration name |\n| `--limit` | Max results (1–100, default 15) |\n| `--cursor` | Pagination token from a previous response |\n| `-o, --output` | Output format: `table` (default) or `json` |\n\n**Response fields:**\n\n| Field | Description |\n|-------|-------------|\n| `id` | Base64 integration ID — copy this for downstream commands |\n| `name` | Human-readable name |\n| `provider` | LLM provider enum (see Supported Providers below) |\n| `has_api_key` | `true` if credentials are stored |\n| `model_names` | Allowed model list, or `null` if all models are enabled |\n| `enable_default_models` | Whether default models for this provider are allowed |\n| `function_calling_enabled` | Whether tool/function calling is enabled |\n| `auth_type` | Authentication method: `default`, `proxy_with_headers`, or `bearer_token` |\n\n---\n\n## Get a Specific Integration\n\n```bash\nax ai-integrations get NAME_OR_ID\nax ai-integrations get NAME_OR_ID -o json\nax ai-integrations get NAME_OR_ID --space SPACE   # required when using name instead of ID\n```\n\nUse this to inspect an integration's full configuration or to confirm its ID after creation.\n\n---\n\n## Create an AI Integration\n\nBefore creating, always list integrations first — the user may already have a suitable one:\n\n```bash\nax ai-integrations list --space SPACE\n```\n\nIf no suitable integration exists, create one. The required flags depend on the provider.\n\n### OpenAI\n\n```bash\nax ai-integrations create \\\n  --name \"My OpenAI Integration\" \\\n  --provider openAI \\\n  --api-key $OPENAI_API_KEY\n```\n\n### Anthropic\n\n```bash\nax ai-integrations create \\\n  --name \"My Anthropic Integration\" \\\n  --provider anthropic \\\n  --api-key $ANTHROPIC_API_KEY\n```\n\n### Azure OpenAI\n\n```bash\nax ai-integrations create \\\n  --name \"My Azure OpenAI Integration\" \\\n  --provider azureOpenAI \\\n  --api-key $AZURE_OPENAI_API_KEY \\\n  --base-url \"https://my-resource.openai.azure.com/\"\n```\n\n### AWS Bedrock\n\nAWS Bedrock uses IAM role-based auth. Provide the ARN of the role Arize should assume via `--provider-metadata`:\n\n```bash\nax ai-integrations create \\\n  --name \"My Bedrock Integration\" \\\n  --provider awsBedrock \\\n  --provider-metadata '{\"role_arn\": \"arn:aws:iam::123456789012:role/ArizeBedrockRole\"}'\n```\n\n### Vertex AI\n\nVertex AI uses GCP service account credentials. Provide the GCP project and region via `--provider-metadata`:\n\n```bash\nax ai-integrations create \\\n  --name \"My Vertex AI Integration\" \\\n  --provider vertexAI \\\n  --provider-metadata '{\"project_id\": \"my-gcp-project\", \"location\": \"us-central1\"}'\n```\n\n### Gemini\n\n```bash\nax ai-integrations create \\\n  --name \"My Gemini Integration\" \\\n  --provider gemini \\\n  --api-key $GEMINI_API_KEY\n```\n\n### NVIDIA NIM\n\n```bash\nax ai-integrations create \\\n  --name \"My NVIDIA NIM Integration\" \\\n  --provider nvidiaNim \\\n  --api-key $NVIDIA_API_KEY \\\n  --base-url \"https://integrate.api.nvidia.com/v1\"\n```\n\n### Custom (OpenAI-compatible endpoint)\n\n```bash\nax ai-integrations create \\\n  --name \"My Custom Integration\" \\\n  --provider custom \\\n  --base-url \"https://my-llm-proxy.example.com/v1\" \\\n  --api-key $CUSTOM_LLM_API_KEY\n```\n\n### Supported Providers\n\n| Provider | Required extra flags |\n|----------|---------------------|\n| `openAI` | `--api-key \u003ckey\u003e` |\n| `anthropic` | `--api-key \u003ckey\u003e` |\n| `azureOpenAI` | `--api-key \u003ckey\u003e`, `--base-url \u003cazure-endpoint\u003e` |\n| `awsBedrock` | `--provider-metadata '{\"role_arn\": \"\u003carn\u003e\"}'` |\n| `vertexAI` | `--provider-metadata '{\"project_id\": \"\u003cgcp-project\u003e\", \"location\": \"\u003cregion\u003e\"}'` |\n| `gemini` | `--api-key \u003ckey\u003e` |\n| `nvidiaNim` | `--api-key \u003ckey\u003e`, `--base-url \u003cnim-endpoint\u003e` |\n| `custom` | `--base-url \u003cendpoint\u003e` |\n\n### Optional flags for any provider\n\n| Flag | Description |\n|------|-------------|\n| `--model-name` | Allowed model name (repeat for multiple, e.g. `--model-name gpt-4o --model-name gpt-4o-mini`); omit to allow all models |\n| `--enable-default-models` | Enable the provider's default model list |\n| `--function-calling-enabled` | Enable tool/function calling support |\n| `--auth-type` | Authentication type: `default`, `proxy_with_headers`, or `bearer_token` |\n| `--headers` | Custom headers as JSON object or file path (for proxy auth) |\n| `--provider-metadata` | Provider-specific metadata as JSON object or file path |\n\n### After creation\n\nCapture the returned integration ID (e.g., `TGxtSW50ZWdyYXRpb246MTI6YUJjRA==`) — it is needed for evaluator creation and other downstream commands. If you missed it, retrieve it:\n\n```bash\nax ai-integrations list --space SPACE -o json\n# or by name/ID directly:\nax ai-integrations get NAME_OR_ID\n```\n\n---\n\n## Update an AI Integration\n\n`update` is a partial update — only the flags you provide are changed. Omitted fields stay as-is.\n\n```bash\n# Rename\nax ai-integrations update NAME_OR_ID --name \"New Name\"\n\n# Rotate the API key\nax ai-integrations update NAME_OR_ID --api-key $OPENAI_API_KEY\n\n# Change the model list (replaces all existing model names)\nax ai-integrations update NAME_OR_ID --model-name gpt-4o --model-name gpt-4o-mini\n\n# Update base URL (for Azure, custom, or NIM)\nax ai-integrations update NAME_OR_ID --base-url \"https://new-endpoint.example.com/v1\"\n```\n\nAdd `--space SPACE` when using a name instead of ID. Any flag accepted by `create` can be passed to `update`.\n\n---\n\n## Delete an AI Integration\n\n**Warning:** Deletion is permanent. Evaluators that reference this integration will no longer be able to run.\n\n```bash\nax ai-integrations delete NAME_OR_ID --force\nax ai-integrations delete NAME_OR_ID --space SPACE --force   # required when using name instead of ID\n```\n\nOmit `--force` to get a confirmation prompt instead of deleting immediately.\n\n---\n\n## Troubleshooting\n\n| Problem | Solution |\n|---------|----------|\n| `ax: command not found` | See references/ax-setup.md |\n| `401 Unauthorized` | API key may not have access to this space. Verify key and space ID at https://app.arize.com/admin \u003e API Keys |\n| `No profile found` | Run `ax profiles show --expand`; set `ARIZE_API_KEY` env var or write `~/.arize/config.toml` |\n| `Integration not found` | Verify with `ax ai-integrations list --space SPACE` |\n| `has_api_key: false` after create | Credentials were not saved — re-run `update` with the correct `--api-key` or `--provider-metadata` |\n| Evaluator runs fail with LLM errors | Check integration credentials with `ax ai-integrations get INT_ID`; rotate the API key if needed |\n| `provider` mismatch | Cannot change provider after creation — delete and recreate with the correct provider |\n\n---\n\n## Related Skills\n\n- **arize-evaluator**: Create LLM-as-judge evaluators that use an AI integration → use `arize-evaluator`\n- **arize-experiment**: Run experiments that use evaluators backed by an AI integration → use `arize-experiment`\n\n---\n\n## Save Credentials for Future Use\n\nSee references/ax-profiles.md § Save Credentials for Future Use.\n","references/ax-profiles.md":"# ax Profile Setup\n\nConsult this when authentication fails (401, missing profile, missing API key). Do NOT run these checks proactively.\n\nUse this when there is no profile, or a profile has incorrect settings (wrong API key, wrong region, etc.).\n\n## 1. Inspect the current state\n\n```bash\nax profiles show\n```\n\nLook at the output to understand what's configured:\n- `API Key: (not set)` or missing → key needs to be created/updated\n- No profile output or \"No profiles found\" → no profile exists yet\n- Connected but getting `401 Unauthorized` → key is wrong or expired\n- Connected but wrong endpoint/region → region needs to be updated\n\n## 2. Fix a misconfigured profile\n\nIf a profile exists but one or more settings are wrong, patch only what's broken.\n\n**Never pass a raw API key value as a flag.** Always reference it via the `ARIZE_API_KEY` environment variable. If the variable is not already set in the shell, instruct the user to set it first, then run the command:\n\n```bash\n# If ARIZE_API_KEY is already exported in the shell:\nax profiles update --api-key $ARIZE_API_KEY\n\n# Fix the region (no secret involved — safe to run directly)\nax profiles update --region us-east-1b\n\n# Fix both at once\nax profiles update --api-key $ARIZE_API_KEY --region us-east-1b\n```\n\n`update` only changes the fields you specify — all other settings are preserved. If no profile name is given, the active profile is updated.\n\n## 3. Create a new profile\n\nIf no profile exists, or if the existing profile needs to point to a completely different setup (different org, different region):\n\n**Always reference the key via `$ARIZE_API_KEY`, never inline a raw value.**\n\n```bash\n# Requires ARIZE_API_KEY to be exported in the shell first\nax profiles create --api-key $ARIZE_API_KEY\n\n# Create with a region\nax profiles create --api-key $ARIZE_API_KEY --region us-east-1b\n\n# Create a named profile\nax profiles create work --api-key $ARIZE_API_KEY --region us-east-1b\n```\n\nTo use a named profile with any `ax` command, add `-p NAME`:\n```bash\nax spans export PROJECT -p work\n```\n\n## 4. Getting the API key\n\n**Never ask the user to paste their API key into the chat. Never log, echo, or display an API key value.**\n\nIf `ARIZE_API_KEY` is not already set, instruct the user to export it in their shell:\n\n```bash\nexport ARIZE_API_KEY=\"...\"   # user pastes their key here in their own terminal\n```\n\nThey can find their key at https://app.arize.com/admin \u003e API Keys. Recommend they create a **scoped service key** (not a personal user key) — service keys are not tied to an individual account and are safer for programmatic use. Keys are space-scoped — make sure they copy the key for the correct space.\n\nOnce the user confirms the variable is set, proceed with `ax profiles create --api-key $ARIZE_API_KEY` or `ax profiles update --api-key $ARIZE_API_KEY` as described above.\n\n## 5. Verify\n\nAfter any create or update:\n\n```bash\nax profiles show\n```\n\nConfirm the API key and region are correct, then retry the original command.\n\n## Space\n\nThere is no profile flag for space. Save it as an environment variable — accepts a space **name** (e.g., `my-workspace`) or a base64 space **ID** (e.g., `U3BhY2U6...`). Find yours with `ax spaces list -o json`.\n\n**macOS/Linux** — add to `~/.zshrc` or `~/.bashrc`:\n```bash\nexport ARIZE_SPACE=\"my-workspace\"    # name or base64 ID\n```\nThen `source ~/.zshrc` (or restart terminal).\n\n**Windows (PowerShell):**\n```powershell\n[System.Environment]::SetEnvironmentVariable('ARIZE_SPACE', 'my-workspace', 'User')\n```\nRestart terminal for it to take effect.\n\n## Save Credentials for Future Use\n\nAt the **end of the session**, if the user manually provided any credentials during this conversation **and** those values were NOT already loaded from a saved profile or environment variable, offer to save them.\n\n**Skip this entirely if:**\n- The API key was already loaded from an existing profile or `ARIZE_API_KEY` env var\n- The space was already set via `ARIZE_SPACE` env var\n- The user only used base64 project IDs (no space was needed)\n\n**How to offer:** Use **AskQuestion**: *\"Would you like to save your Arize credentials so you don't have to enter them next time?\"* with options `\"Yes, save them\"` / `\"No thanks\"`.\n\n**If the user says yes:**\n\n1. **API key** — Run `ax profiles show` to check the current state. Then run `ax profiles create --api-key $ARIZE_API_KEY` or `ax profiles update --api-key $ARIZE_API_KEY` (the key must already be exported as an env var — never pass a raw key value).\n\n2. **Space** — See the Space section above to persist it as an environment variable.\n","references/ax-setup.md":"# ax CLI — Troubleshooting\n\nConsult this only when an `ax` command fails. Do NOT run these checks proactively.\n\n## Check version first\n\nIf `ax` is installed (not `command not found`), always run `ax --version` before investigating further. The version must be `0.14.0` or higher — many errors are caused by an outdated install. If the version is too old, see **Version too old** below.\n\n## `ax: command not found`\n\n**macOS/Linux:**\n1. Check common locations: `~/.local/bin/ax`, `~/Library/Python/*/bin/ax`\n2. Install: `uv tool install arize-ax-cli` (preferred), `pipx install arize-ax-cli`, or `pip install arize-ax-cli`\n3. Add to PATH if needed: `export PATH=\"$HOME/.local/bin:$PATH\"`\n\n**Windows (PowerShell):**\n1. Check: `Get-Command ax` or `where.exe ax`\n2. Common locations: `%APPDATA%\\Python\\Scripts\\ax.exe`, `%LOCALAPPDATA%\\Programs\\Python\\Python*\\Scripts\\ax.exe`\n3. Install: `pip install arize-ax-cli`\n4. Add to PATH: `$env:PATH = \"$env:APPDATA\\Python\\Scripts;$env:PATH\"`\n\n## Version too old (below 0.14.0)\n\nUpgrade: `uv tool install --force --reinstall arize-ax-cli`, `pipx upgrade arize-ax-cli`, or `pip install --upgrade arize-ax-cli`\n\n## SSL/certificate error\n\n- macOS: `export SSL_CERT_FILE=/etc/ssl/cert.pem`\n- Linux: `export SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt`\n- Fallback: `export SSL_CERT_FILE=$(python -c \"import certifi; print(certifi.where())\")`\n\n## Subcommand not recognized\n\nUpgrade ax (see above) or use the closest available alternative.\n\n## Still failing\n\nStop and ask the user for help.\n"},"import":{"commit_sha":"541b7819d8c3545c6df122491af4fa1eae415779","imported_at":"2026-05-18T20:05:35Z","license_text":"MIT License\n\nCopyright GitHub, Inc.\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.","owner":"github","repo":"github/awesome-copilot","source_url":"https://github.com/github/awesome-copilot/tree/541b7819d8c3545c6df122491af4fa1eae415779/plugins/arize-ax/skills/arize-ai-provider-integration"}},"content_hash":[169,16,103,160,188,26,169,207,226,112,40,97,94,239,58,56,227,109,142,243,198,161,49,72,143,32,162,67,11,252,99,229],"trust_level":"unsigned","yanked":false}