[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AD61T6FR5E5ETTN5WN0VR4":3,"skill-same:01M6AD61T6FR5E5ETTN5WN0VR4":85},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6AD61T6FR5E5ETTN5WN0VR4","arize-ai-provider-integration",null,"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.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41081,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Farize-ai-provider-integration\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"provider","integration","arize ai provider integration","Arize","provider integration","nvidia nim","cli","when","features","updates","nim","bedrock","ax","list","credentials","openai","update","delete","create","azure openai","azure","vertex ai","gemini","2026-11-10 10:12:30",false,"---\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> **`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> **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\u002Fax-setup.md\n- `401 Unauthorized` \u002F 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\u002Fax-profiles.md to create\u002Fupdate it. If the user doesn't have their key, direct them to https:\u002F\u002Fapp.arize.com\u002Fadmin > 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 \u002F 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\u002Ffunction 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:\u002F\u002Fmy-resource.openai.azure.com\u002F\"\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\u002FArizeBedrockRole\"}'\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:\u002F\u002Fintegrate.api.nvidia.com\u002Fv1\"\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:\u002F\u002Fmy-llm-proxy.example.com\u002Fv1\" \\\n  --api-key $CUSTOM_LLM_API_KEY\n```\n\n### Supported Providers\n\n| Provider | Required extra flags |\n|----------|---------------------|\n| `openAI` | `--api-key \u003Ckey>` |\n| `anthropic` | `--api-key \u003Ckey>` |\n| `azureOpenAI` | `--api-key \u003Ckey>`, `--base-url \u003Cazure-endpoint>` |\n| `awsBedrock` | `--provider-metadata '{\"role_arn\": \"\u003Carn>\"}'` |\n| `vertexAI` | `--provider-metadata '{\"project_id\": \"\u003Cgcp-project>\", \"location\": \"\u003Cregion>\"}'` |\n| `gemini` | `--api-key \u003Ckey>` |\n| `nvidiaNim` | `--api-key \u003Ckey>`, `--base-url \u003Cnim-endpoint>` |\n| `custom` | `--base-url \u003Cendpoint>` |\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\u002Ffunction 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\u002FID 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:\u002F\u002Fnew-endpoint.example.com\u002Fv1\"\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\u002Fax-setup.md |\n| `401 Unauthorized` | API key may not have access to this space. Verify key and space ID at https:\u002F\u002Fapp.arize.com\u002Fadmin > API Keys |\n| `No profile found` | Run `ax profiles show --expand`; set `ARIZE_API_KEY` env var or write `~\u002F.arize\u002Fconfig.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\u002Fax-profiles.md § Save Credentials for Future Use.\n","# Arize AI Integration Skill\n\n> **`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> **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\u002Fax-setup.md\n- `401 Unauthorized` \u002F 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\u002Fax-profiles.md to create\u002Fupdate it. If the user doesn't have their key, direct them to https:\u002F\u002Fapp.arize.com\u002Fadmin > 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 \u002F 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\u002Ffunction 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:\u002F\u002Fmy-resource.openai.azure.com\u002F\"\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\u002FArizeBedrockRole\"}'\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:\u002F\u002Fintegrate.api.nvidia.com\u002Fv1\"\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:\u002F\u002Fmy-llm-proxy.example.com\u002Fv1\" \\\n  --api-key $CUSTOM_LLM_API_KEY\n```\n\n### Supported Providers\n\n| Provider | Required extra flags |\n|----------|---------------------|\n| `openAI` | `--api-key \u003Ckey>` |\n| `anthropic` | `--api-key \u003Ckey>` |\n| `azureOpenAI` | `--api-key \u003Ckey>`, `--base-url \u003Cazure-endpoint>` |\n| `awsBedrock` | `--provider-metadata '{\"role_arn\": \"\u003Carn>\"}'` |\n| `vertexAI` | `--provider-metadata '{\"project_id\": \"\u003Cgcp-project>\", \"location\": \"\u003Cregion>\"}'` |\n| `gemini` | `--api-key \u003Ckey>` |\n| `nvidiaNim` | `--api-key \u003Ckey>`, `--base-url \u003Cnim-endpoint>` |\n| `custom` | `--base-url \u003Cendpoint>` |\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\u002Ffunction 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\u002FID 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:\u002F\u002Fnew-endpoint.example.com\u002Fv1\"\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\u002Fax-setup.md |\n| `401 Unauthorized` | API key may not have access to this space. Verify key and space ID at https:\u002F\u002Fapp.arize.com\u002Fadmin > API Keys |\n| `No profile found` | Run `ax profiles show --expand`; set `ARIZE_API_KEY` env var or write `~\u002F.arize\u002Fconfig.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\u002Fax-profiles.md § Save Credentials for Future Use.\n",{"name":5,"metadata":47,"description":7,"compatibility":50},{"author":48,"version":49},"arize","1.0","Requires the ax CLI and a configured Arize profile.","main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Farize-ai-provider-integration",5344,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-13 02:05:36",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add github\u002Fawesome-copilot --skill arize-ai-provider-integration",{"tool":67,"command":68},"bunx","bunx skills add github\u002Fawesome-copilot --skill arize-ai-provider-integration",{"tool":70,"command":71},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill arize-ai-provider-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Farize-ai-provider-integration\u002FSKILL.md",true,[75,81],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fax-profiles.md","REFERENCE","参考文档",4605,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Farize-ai-provider-integration\u002Freferences\u002Fax-profiles.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fax-setup.md",1529,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Farize-ai-provider-integration\u002Freferences\u002Fax-setup.md",[86,120,148,177,210,227],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":100,"publishedAt":42},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[92,97],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":98,"categoryName":99,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000023","Skill与智能体开发",[101,102,103,104,105,26,106,107,108,109,110,111,112,113,114,115,116,117,118,119],"supabase","rls","supabase rls","supabase rls policies","project","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":127,"publishedAt":42},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[126],{"categoryNo":98,"categoryName":99,"taxonomyType":95,"taxonomyTypeDesc":96},[128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":152,"sourceHtmlUrl":153,"categories":154,"keywords":160,"publishedAt":42},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[155],{"categoryNo":156,"categoryName":157,"taxonomyType":158,"taxonomyTypeDesc":159},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[161,162,163,164,165,166,134,105,167,168,169,39,170,171,172,116,173,174,175,176],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":181,"sourceHtmlUrl":182,"categories":183,"keywords":188,"publishedAt":42},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[184,187],{"categoryNo":185,"categoryName":186,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":156,"categoryName":157,"taxonomyType":158,"taxonomyTypeDesc":159},[189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,26,27,204,205,206,207,134,208,209],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","full","camera","events","platform","methods","controls",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":214,"licenseFileUrl":215,"sourceHtmlUrl":216,"categories":217,"keywords":223,"publishedAt":42},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[218,219,222],{"categoryNo":185,"categoryName":186,"taxonomyType":95,"taxonomyTypeDesc":96},{"categoryNo":220,"categoryName":221,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":98,"categoryName":99,"taxonomyType":95,"taxonomyTypeDesc":96},[224,131,198,225,226],"resemble detect","https","identity",{"skillNo":228,"name":229,"nameZh":6,"description":230,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":214,"licenseFileUrl":231,"sourceHtmlUrl":232,"categories":233,"keywords":238,"publishedAt":42},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[234,237],{"categoryNo":235,"categoryName":236,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":98,"categoryName":99,"taxonomyType":95,"taxonomyTypeDesc":96},[239,240,241,242,162,106,9,130,243,244,225,245,246,247,248,249,250,251,252,253,254,255,114,256,257,258,259],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]