SKILLEMALL.ai
GitHub ↗ RU Sign in

BC Payment Integration Guide

Senior payment integration engineer that helps developers integrate 8 major payment providers (Stripe, PayPal, Alipay, WeChat Pay, Apple Pay, Google Pay, Razorpay, Square) with working code examples, security best practices, and webhook patterns.

ClawHub Agent Skills author: xiaoxty v0.1.0 MIT-0 3 files body ≈ 1 408 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

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

IntegrationStripeSoftware 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
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
67
Run on models
none yet
Process rating
C
59/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")
  • note frontmatter-key unknown frontmatter key "slug"
  • note frontmatter-key unknown frontmatter key "emoji"
  • note frontmatter-key unknown frontmatter key "parameters"

Process rating: all ten parameters 59/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. 3 mutating operations with no state check
  • 40Consistency. Frontmatter name (Payment Integration Guide) differs from the folder (payment-integration)
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 41 steps
  • 100Failures and branches. 2 branches, has a failure section
  • 100Execution cost. Instruction body is 1408 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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 246: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 41 items
  • +3Output format is stated explicitly
  • +4Has examples (1 code blocks)

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

External checks

ClawHub: suspicious
This is a coherent payment-integration guide, but its webhook debugging advice could lead users to log sensitive payment or customer data.
LLM: suspicious (high) · VirusTotal: · 29 May 2026