SkillSpector supports hosted providers like OpenAI, Anthropic, Bedrock, and NVIDIA Build, but does not support Google Gemini out of the box.
Currently, Google's Gemini platform (or whatever the current naming is) is not supported without some cumbersome workarounds and static API keys outside IAM controls.
Proposed Solution:
Add a native SKILLSPECTOR_PROVIDER=gemini provider that:
- Authenticates using Google Cloud ADC (
google-auth), supporting local development (gcloud auth application-default login) and GKE Workload Identity seamlessly
- Connects to Google Cloud's OpenAI-compatible Gemini endpoint (
aiplatform.googleapis.com/v1/.../endpoints/openapi), reusing the existing chat-model plumbing
- Automatically applies the
google/ wire prefix while keeping bare model names in registries and user config
- Correctly routes
global, us, eu, and regional endpoints
- Fails closed with an actionable error when
GOOGLE_CLOUD_PROJECT is missing (without silently falling back to OPENAI_API_KEY)
- Ships a bundled
model_registry.yaml with current Gemini 3.x/2.5 token limits
(Note: PR #12 previously explored Vertex AI support, but has become stale and conflicting, uses their old naming, outdated models, and doesn't cover as many cases. I think that fresh implementation targeting Google's current v1 Gemini endpoint and modern conventions would resolve this cleanly.)
SkillSpector supports hosted providers like OpenAI, Anthropic, Bedrock, and NVIDIA Build, but does not support Google Gemini out of the box.
Currently, Google's Gemini platform (or whatever the current naming is) is not supported without some cumbersome workarounds and static API keys outside IAM controls.
Proposed Solution:
Add a native
SKILLSPECTOR_PROVIDER=geminiprovider that:google-auth), supporting local development (gcloud auth application-default login) and GKE Workload Identity seamlesslyaiplatform.googleapis.com/v1/.../endpoints/openapi), reusing the existing chat-model plumbinggoogle/wire prefix while keeping bare model names in registries and user configglobal,us,eu, and regional endpointsGOOGLE_CLOUD_PROJECTis missing (without silently falling back toOPENAI_API_KEY)model_registry.yamlwith current Gemini 3.x/2.5 token limits(Note: PR #12 previously explored Vertex AI support, but has become stale and conflicting, uses their old naming, outdated models, and doesn't cover as many cases. I think that fresh implementation targeting Google's current v1 Gemini endpoint and modern conventions would resolve this cleanly.)