SKILLEMALL.ai
GitHub ↗ RU Sign in

AC alapi

ALAPI 接口对接助手。帮助开发者搜索 ALAPI 接口、读取 ALAPI 文档、提取参数、生成 ALAPI 对接代码，并在用户明确提供 token 且确认后调用 ALAPI 接口。当用户提到 "ALAPI"、"alapi.cn"、ALAPI 文档 URL、ALAPI token、ALAPI 接口示例、或希望接入 ALAPI 平台接口时触发。

ClawHub Agent Skills author: Alone88 v1.0.0 MIT-0 8 files body ≈ 989 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
98
Quality 40%
79
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • 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 exfil-secret-in-url references/code-examples.md:17
    Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)
    curl "https://v3.alapi.cn/api/{PATH}?token=…&key=value"
    placeholder
  • low Exfiltration net-credential-use references/code-examples.md:17
    Credential used in a network call (verify the destination is the intended service) (test fixture / example file; the skill's own vendor host)
    curl "https://v3.alapi.cn/api/{PATH}?token=…&key=value"
    fixturevendor-host

Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 51/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
  • 20When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (web, python) that frontmatter does not declare
  • 100Steps. 54 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 989 tokens
  • 100Running it twice. No mutating operations
  • medium 5 test cases, all positive: not one "should refuse" or "should ask first"
  • low No test case covers injection arriving through data

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
  • +1No license
  • +2Single-language instructions
  • +3Description length 173: enough signal without eating the budget
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 54 items
  • +4Has examples (7 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +3All 1 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.

External checks

ClawHub: suspicious
The skill appears to use an external API token in a way that may happen from the local environment rather than only by explicit user-provided consent.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026