SKILLEMALL.ai
GitHub ↗ RU Sign in

CC ZL-ClawPay

支付技能：支持免密支付、订单查询、交易流水等功能。 触发词：发起订单支付、执行订单付款、提交支付订单、确认订单支付、完成账单支付、查询支付订单状态、查询交易流水记录、绑定子钱包、验证钱包凭据、解绑子钱包、撤销钱包绑定。 不适用于：非支付场景、历史数据导出、批量操作、余额查询、收款码生成。 基于 Node.js 实现，使用 SM2/SM3/SM4 国密算法加密通信。

Not recommendedcritical or high security findings
ClawHub Agent Skills author: zlpay v1.0.9 MIT-0 20 files body ≈ 1 502 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 53/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
C
74/100
safety, quality, tests
Safety 60%
79
Quality 40%
66
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Secrets in code
If you install

The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.

For the author

The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. 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
  • 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 · 4

  • high Secrets in code meta-credential-files config/.env
    Credential / dotenv files bundled with the skill (1)
    config/.env
Medium and low: 3
  • low Secrets in code secret-labelled-token assets/request-examples.md:75
    Labelled token / key literal (vendor format unknown — verify it is not a live credential) (placeholder value)
    --apiKey=your…key \
    placeholder
  • low Exfiltration read-dotenv scripts/config.js:17
    Reads a .env file (quoted — discussed, not commanded)
    `     Fix: Copy config/.env.example to config/.env and fill in the values.\n` +
    quoted
  • low Exfiltration read-dotenv scripts/skill.js:119
    Reads a .env file (quoted — discussed, not commanded)
    `  Fix: Copy config/.env.example to config/.env, or re-package with pack…s1.`
    quoted

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

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "skill_type"
  • note frontmatter-key unknown frontmatter key "execution_mode"
  • note frontmatter-key unknown frontmatter key "has_server"
  • note frontmatter-key unknown frontmatter key "has_install_scripts"
  • note frontmatter-key unknown frontmatter key "environment_variables"

Process rating: all ten parameters 53/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 100Tools and files. No external tools needed
  • 100Steps. 47 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1502 tokens
  • 100Running it twice. No mutating operations

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
  • -34 of 5 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +3Description length 183: enough signal without eating the budget
  • +4Structure: 28 headings
  • +3Step-by-step instructions: 47 items
  • +4Has examples (2 code blocks)
  • +4Reference files are cited in the instructions (4 of 4)
  • +1License stated

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

External checks

ClawHub: suspicious
This payment skill needs manual review because it can use stored payment credentials for live payment actions and the supplied evidence shows weak confirmation and credential safeguards.
LLM: suspicious (medium) · VirusTotal: · 2 Jun 2026