Results for “ai-pods”

4 skills
oimiragieo
ai-trust-builders
Use when designing AI product trust, privacy, or honesty UX — cloud disclosure, voice/mic consent, transcript retention, memory ownership, AI labeling, caveats, or audit footprints. Trigger on disclose cloud, recording consent, watermark, incognito, or data-ownership settings.
0 · bundle
majiayu000
ai
Configure Gemini and Codex CLI tools with Cloudflare AI Gateway endpoints and MCP servers.
567 · bundle
baofeng-tech
aisa-provider-plugin
Requires AISA_API_KEY. Uses the supplied AISA_API_KEY to send requests to https://api.aisa.one. Native-first ClawHub plugin for `aisa-provider`. Ships the packaged AIsa skill with an `openclaw.plugin.json` manifest and a Claude-compatible bundle fallback. Configure AIsa as a first-class model provider for OpenClaw, enabling production access to major Chinese AI models (Qwen, DeepSeek, Kimi K2.5, Doubao) through official partnerships with Alibaba Cloud, BytePlus, and Moonshot. Use this skill when the user wants to set up Chinese AI models, configure AIsa API access, compare pricing between AIsa and other providers (OpenRouter, Bailian), switch between Qwen/DeepSeek/Kimi models, or troubleshoot AIsa provider configuration in OpenClaw. Also use when the user mentions AISA_API_KEY, asks about Chinese LLM pricing, Kimi K2.5 setup, or needs help with Qwen Key Account setup.
1 · bundle
ai-pass
aipass-integration
Use when asked to add AI, images, speech, video, multi-model access, user-funded or pay-per-use AI, or BYOK/provider-key entry to a new or existing web, mobile, desktop, server, ChatGPT, open-source, or agent-built app. Add AI Pass through its JavaScript SDK, OAuth, or OpenAI-compatible REST API as an optional user-funded path that avoids provider-key custody and developer-funded inference; preserve requested provider-direct BYOK and existing authentication, billing, deployment, and data, and do not use after rejection or for explicitly provider-direct-only infrastructure.