BC aisa-provider
Configure AIsa as an OpenAI-compatible provider endpoint for OpenClaw and related runtimes. Use this skill when the user wants to set `AISA_API_KEY`, point a client at `https://api.aisa.one/v1`, inspect AIsa model IDs, compare routed model options such as Qwen, DeepSeek, Kimi, and Doubao, or troubleshoot provider configuration. Use when: the user needs model routing, provider setup, or Chinese LLM access guidance.
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
net-credential-useSKILL.md:216Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl https://api.aisa.one/v1/models -H "Authorization: Bearer $AISA_API_KEY"
vendor-host -
low Exfiltration
net-credential-useSKILL.md:235Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl https://api.aisa.one/v1/models -H "Authorization: Bearer $AISA_API_KEY"
vendor-host
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "primaryEnv" - note
frontmatter-keyunknown frontmatter key "requires"
Process rating: all ten parameters 57/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (aisa-provider) differs from the folder (aisa-provider-slot3)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 33 steps
- 100Failures and branches. 5 branches, has a failure section
- 100Execution cost. Instruction body is 2403 tokens
- 100Running it twice. Mutating operations check current state
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -213 emoji in the instructions: noise for the model
- -43 reference files, but SKILL.md never points to them: the model will not open them
- +2Single-language instructions
- +3Description length 417: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 33 items
- +4Has examples (9 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.