SKILLEMALL.ai
RU Sign in

BC HONGKONG-PAYMENT-QFPAY

QFPay API is a comprehensive payment solution that offers various payment methods to meet the needs of different businesses. This skill provides complete API integration guidelines including environment configuration, request formats, signature generation, payment types, supported currencies, and status codes.

ClawHub Agent Skills author: xingstudy v1.0.0 3 files body ≈ 4 775 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process C 62/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice

IntegrationSoftware developmentInfrastructuretype 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
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
70
Run on models
none yet
Process rating
C
62/100
Has gaps
Inputs and preconditions w 11
0
When it triggers w 12
20
Running it twice w 4
30
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
  • 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 · 0

✓ No critical or high findings

Files scanned: 3. 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")

Process rating: all ten parameters 62/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 17 mutating operations with no state check
  • 60Tools and files. Uses tools (web, python) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Execution cost. Instruction body is 4775 tokens
  • 100Steps. 40 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 13 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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 311: enough signal without eating the budget
  • +4Structure: 39 headings
  • +3Step-by-step instructions: 40 items
  • +3Output format is stated explicitly
  • +4Has examples (11 code blocks)

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

External checks

ClawHub: clean
This is a documentation-only QFPay payment integration skill, with expected payment and credential guidance but no evidence of hidden execution or data misuse.
LLM: benign (high) · VirusTotal: benign · 28 May 2026