← ClaudeAtlas

setup-ai-operationslisted

Configure optional Microsoft Foundry, Hugging Face, and ElevenLabs provider access for AI Operations. Use after installing the plugin, when a provider is unavailable, when auditing authentication, or when previewing and provisioning the exact ElevenLabs private runtime.
fabioc-aloha/Alex_Skill_Mall · ★ 4 · AI & Automation · score 77
Install: claude install-skill fabioc-aloha/Alex_Skill_Mall
# Setup AI Operations Configure only the providers the user chooses. Plugin installation is not authorization to authenticate providers, install Python packages, or spend credits. ## Onboarding Boundary Onboarding ends after plugin installation and component verification. During onboarding, do not ask for API keys, tokens, or other credentials, do not initiate provider login, and do not provision a provider runtime. Report that planning is available without credentials. Defer provider login and authentication until an approved execution plan selects a provider and execution requires access. ## Procedure 1. Determine whether this is onboarding or just-in-time preparation for a selected execution. 2. During onboarding, inspect the MCP definitions, report all three providers as unverified, state that planning is ready, and stop without authentication or provisioning. 3. After an approved plan selects a provider and execution requires access, configure only that provider. 4. For Foundry, start `aiops-foundry` at `https://mcp.ai.azure.com` and complete Microsoft Entra ID login. Confirm an Azure subscription, Foundry project, and Contributor-or-higher access before execution. 5. For Hugging Face, start `aiops-huggingface` and complete the first-party login flow. Provider settings control enabled Hub and Space tools. 6. Keep all provider credentials optional during installation and planning. Do not request or validate an API key until the user has select