skilld
All skills
github avatar

/arize-ai-provider-integration

@4e136f3 official
by githubgithub/awesome-copilot40k stars
5,040

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.

Ask your Agent

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/arize-ai-provider-integration

This session only. Nothing lands on disk.

referencesax-setup.md

≈383 tokens on demand. Your agent reads this file only when SKILL.md points to it.

ax CLI — Troubleshooting

Consult this only when an ax command fails. Do NOT run these checks proactively.

Check version first

If 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.

ax: command not found

macOS/Linux:

  1. Check common locations: ~/.local/bin/ax, ~/Library/Python/*/bin/ax
  2. Install: uv tool install arize-ax-cli (preferred), pipx install arize-ax-cli, or pip install arize-ax-cli
  3. Add to PATH if needed: export PATH="$HOME/.local/bin:$PATH"

Windows (PowerShell):

  1. Check: Get-Command ax or where.exe ax
  2. Common locations: %APPDATA%\Python\Scripts\ax.exe, %LOCALAPPDATA%\Programs\Python\Python*\Scripts\ax.exe
  3. Install: pip install arize-ax-cli
  4. Add to PATH: $env:PATH = "$env:APPDATA\Python\Scripts;$env:PATH"

Version too old (below 0.14.0)

Upgrade: uv tool install --force --reinstall arize-ax-cli, pipx upgrade arize-ax-cli, or pip install --upgrade arize-ax-cli

SSL/certificate error

  • macOS: export SSL_CERT_FILE=/etc/ssl/cert.pem
  • Linux: export SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt
  • Fallback: export SSL_CERT_FILE=$(python -c "import certifi; print(certifi.where())")

Subcommand not recognized

Upgrade ax (see above) or use the closest available alternative.

Still failing

Stop and ask the user for help.

Source: SKILL.md on GitHub

Third-party checks

No alerts16d4 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    This skill is designed to manage Arize AI integrations using the ax CLI. It follows security best practices for credential handling by using environment variables and providing explicit warnings against reading local secret files. The skill includes standard configuration steps for CLI tools, such as persisting workspace preferences in shell profiles and installing the official ax tool. A minor vulnerability surface for indirect prompt injection exists because the agent processes output from a remote service without explicit boundary markers.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • ZeroLeaks5mo

    1 finding · Score: 86/100

Provenance

Signed by skilld at 4e136f3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 5 months ago

Capability

metadata
{
  "author": "arize",
  "version": "1.0"
}
compatibility
Requires the ax CLI and a configured Arize profile.

Topics

  • Auth
  • arize
  • llm
  • credentials
  • integrations
  • openai
  • anthropic
  • bedrock
  • vertex-ai
  • api-key

README badge

README badge for github/awesome-copilot/arize-ai-provider-integration

What it does

Manages Arize AI integrations for storing LLM provider credentials used by evaluators. Supports OpenAI, Anthropic, Azure OpenAI, AWS Bedrock, Vertex AI, Gemini, NVIDIA NIM, and custom OpenAI-compatible endpoints via the ax CLI. Use this skill to create, list, update, or delete integrations that allow Arize to invoke LLM providers on your behalf.

Generated from the current SKILL.md.

Frequently asked

What LLM providers does this skill support?
OpenAI, Anthropic, Azure OpenAI, AWS Bedrock, Vertex AI, Gemini, NVIDIA NIM, and custom OpenAI-compatible endpoints.
Do I need to specify which space an integration belongs to when creating one?
No. The `create` command does not accept a `--space` flag — AI integrations are account-scoped. Use `--space` only with `list`, `get`, `update`, and `delete`.
How do I find an integration ID after creating one?
The integration ID is returned immediately after creation. If you missed it, run `ax ai-integrations list --space SPACE -o json` or `ax ai-integrations get NAME_OR_ID` to retrieve it.
Can I change the provider of an existing integration?
No. You must delete the integration and create a new one with the correct provider.
What happens to evaluators if I delete an integration?
Evaluators that reference the deleted integration will no longer be able to run. Deletion is permanent.

Generated from the current SKILL.md. These answers refresh after source changes.