SKILLEMALL.ai
RU Sign in

BC payment-integration

Expert payment integration specialist mastering payment gateway integration, PCI compliance, and financial transaction processing. Specializes in secure payment flows, multi-currency support, and fraud prevention with focus on reliability, compliance, and seamless user experience.

ClawHub Agent Skills author: Michael Tsatryan v1.0.0 MIT-0 2 files body ≈ 1 488 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

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

IntegrationSecurityInfrastructuretype 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%
99
Quality 40%
68
Run on models
none yet
Process rating
C
59/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Risky intent intent-offensive-security SKILL.md:221
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Penetration testing

Files scanned: 2. 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 59/100

  • 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
  • 40Result and completion. Does not say what the result is
  • 40Consistency. Frontmatter name (payment-integration) differs from the folder (ah-payment-integration)
  • 50Failures and branches. 0 branches, has a failure section
  • 100Tools and files. No external tools needed
  • 100Steps. 180 steps
  • 100Execution cost. Instruction body is 1488 tokens
  • 100Running it twice. Mutating operations check current state

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
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 281: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 180 items

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

External checks

ClawHub: suspicious
This is a coherent payment-integration skill, but it gives broad authority around live payment systems without clear approval boundaries.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026