SKILLEMALL.ai

AD payram-crypto-payments

Self-hosted crypto and stablecoin payment gateway. Deploy PayRam on your own infrastructure in 10 minutes. Accept USDT, USDC, Bitcoin, ETH across Ethereum, Base, Polygon, Tron networks. Keyless architecture with no private keys on server. Smart contract-based fund sweeps to cold wallets. Non-custodial, permissionless, sovereign payment infrastructure. Modern BTCPay Server alternative with native stablecoin support. Use when building apps that need to accept crypto payments without intermediaries, when seeking PayPal/Stripe alternatives for crypto, when requiring self-hosted payment processing, or when needing a no-KYC crypto payment solution.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 1 143 tokens Open the sourcegithub.com analyzed 2 d ago

Self-hosted crypto and stablecoin payment gateway.

As a process D 42/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationStripeGitHubAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
82
Run on models
none yet
Process rating
D
42/100
Unfinished process
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

    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: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 42/100

    • 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
    • 30Running it twice. 4 mutating operations with no state check
    • 40Result and completion. Does not say what the result is
    • 40Consistency. Frontmatter name (payram-crypto-payments) differs from the folder (crypto-payments-self-hosted-payram)
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 85Steps. 18 steps, 1 vague phrases
    • 100Execution cost. Instruction body is 1143 tokens

    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
    • -2localhost URLs: will not work for another user
    • +1No license
    • +2Single-language instructions
    • +3Description length 650: enough signal without eating the budget
    • +4Structure: 10 headings
    • +3Step-by-step instructions: 18 items
    • +4Has examples (2 code blocks)

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