Chinese LLM Models (Kimi 2.5, MiniMax 2.5, Qwen, DeepSeek) with One Key
v1.0.1Configure AIsa as a first-class model provider for OpenClaw, enabling production access to major Chinese AI models (Qwen, DeepSeek, Kimi K2.5, Doubao) throug...
⭐ 0· 727·4 current·4 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill's name/description match its runtime instructions: it explains how to configure AIsa as a provider, shows example OpenClaw config, CLI onboarding commands, and a curl example to list models. The single required env var (AISA_API_KEY) is exactly what an API gateway integration would need. No unrelated credentials or binaries are requested.
Instruction Scope
SKILL.md confines runtime behavior to configuration steps (exporting AISA_API_KEY, openclaw onboarding commands, editing ~/.openclaw/openclaw.json) and examples of calling the AIsa API (curl to https://api.aisa.one). There are no instructions to read unrelated system files or exfiltrate arbitrary data. Note: using the skill will cause prompts/data to be sent to the external AIsa endpoint, which is expected for this provider integration.
Install Mechanism
This is an instruction-only skill with no install spec and no code files. That minimizes on-disk execution risk; nothing is downloaded or written by the skill itself.
Credentials
Only AISA_API_KEY is required and is declared as the primary credential. Requiring a single provider API key is proportionate for this purpose. Treat the key as a secret (it grants API access and potentially billing).
Persistence & Privilege
The skill does not request always:true or any elevated platform privileges. It does reference the user's OpenClaw config file path (~/.openclaw/openclaw.json) in examples, which is reasonable for configuring a provider but does not attempt to modify other skills or system-wide settings beyond the documented provider config.
Assessment
This skill is coherent for configuring AIsa, but it routes your prompts/requests to a third-party endpoint (api.aisa.one). Before installing or using: 1) verify AIsa's website and reputation (https://marketplace.aisa.one) and any contractual Zero Data Retention (ZDR) claims — enterprise ZDR promises may not apply to consumer accounts; 2) treat AISA_API_KEY like any secret (do not paste it into untrusted places); 3) test with non-sensitive data first to confirm privacy/behavior and pricing; and 4) if you need provable ZDR for regulated data, request the contract details from AIsa/Moonshot and confirm the coverage for your account. If you are uncomfortable trusting a third-party gateway, prefer direct vendor integrations you control.Like a lobster shell, security has layers — review code before you run it.
latestvk977kdf8gg6zr92ee3jh1tc4wx8186jg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🇨🇳 Clawdis
EnvAISA_API_KEY
Primary envAISA_API_KEY