By payabli
Agent Skills for integrating with Payabli — Pay In, Pay Out, webhooks, tokenization, subscriptions, and more. Ships Payabli-specific procedural knowledge into your coding agent.
Use when writing code that accepts payments through Payabli: charging cards or ACH, integrating embedded payment components or a hosted payment page, handling Apple Pay or Google Pay, or processing voids and refunds. Boundaries — subscriptions: payabli-subscriptions; invoices and payment links: payabli-invoices; disputes and refund-failure recovery: payabli-disputes. Reads payabli-integration.md on load if present.
Use when building accounts-payable automation on Payabli — capturing vendor bills (manual entry or OCR), routing them through approval, and paying them through Pay Out. Distinct from raw payouts (payabli-send-payments): a bill starts with a vendor invoice that may need approval before payment. Reads payabli-integration.md on load if present.
Use when a partner wants to rehearse the Payabli certification test scenarios in sandbox before their certification call — running the checks they can self-serve and confirming expected results. This is prep for the call, not self-certification (certification happens with a Payabli SE). Reads payabli-integration.md on load if present.
Use when working with Payabli customer records — creating, reading, listing or searching, updating, or deleting customers, or showing a customer's transaction history (any CRM or customer portal). Covers the Customer API and customer queries. Money movement lives in payabli-accept-payments, saved payment methods in payabli-tokenization, recurring billing in payabli-subscriptions, and Pay Out vendors in payabli-vendors. Reads payabli-integration.md on load if present.
Use when handling chargebacks or transaction returns on Payabli — responding to disputes, submitting evidence, processing ACH return codes, or recovering from a failed refund. Routine voids/refunds of healthy transactions are NOT here — those live in payabli-accept-payments. Reads payabli-integration.md on load if present.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Status: beta. The skills are live and growing — we're adding coverage and refining as partners put them to work, so expect changes.
Agent Skills that Payabli partners install in their coding agent to integrate Payabli — from building the integration through getting ready for your certification call — without hands-on integration support. They work in any agent that supports the open Agent Skills standard, including Claude Code, Cursor, Codex, GitHub Copilot, and Gemini CLI.
Skills ship Payabli-specific procedural knowledge directly into your coding agent: the order of operations, the decisions that matter, and the patterns that keep a payments integration correct. They load just-in-time, when your agent is about to write Payabli-touching code.
Skills are complementary to the official Payabli Docs MCP server: the MCP answers questions (Q&A), skills sequence the work. Both read from the same source of truth — docs.payabli.com — so they converge on the same answers.
Use AI responsibly. These skills are crafted by the Payabli team, and they steer an AI coding agent inside your environment. AI output isn't perfect — review and verify everything your agent generates against the official docs (
docs.payabli.com) and your sandbox before you ship it, and reach out to your Payabli integration contact if something looks wrong or you need confirmation. Never paste or save secrets (API keys, tokens, cardholder data) into your agent or commit them to your repo; use sandbox credentials and environment variables.
Jump to: The skill set · What you'll need · Install · Usage · Repo structure · Resources · Contributing
Organized by what you're building, not by Payabli's product taxonomy.
| Skill | What it's for |
|---|---|
payabli-getting-started | Design/onboarding entry point; maps your capability goal to the Payabli pieces and writes an integration plan |
payabli-fundamentals | Auth, IDs, paypoint scoping, idempotency, error handling — loaded by every other skill |
payabli-accept-payments | Pay In core: cards, ACH, wallets, embedded components, hosted pages |
payabli-customers | Customer records: create, read, list/search, update, delete, transaction history |
payabli-subscriptions | Recurring billing, autopay, dunning |
payabli-invoices | Invoices and customer-facing payment links |
payabli-disputes | Chargebacks, evidence, refund failures |
payabli-send-payments | Pay Out core: payouts, reissue |
payabli-vendors | Vendor records: create, read, list/search, update, delete, payment history |
payabli-bills | AP automation: bill capture, OCR, approvals |
payabli-webhooks | Webhook handling and event processing |
payabli-tokenization | Saved payment methods (Pay In and Pay Out) |
payabli-reporting | Query API for reports and list/detail data UIs, reconciliation, settlement tracking |
payabli-testing | Sandbox usage, test data, and event simulation |
payabli-certification-prep | Rehearse the certification test scenarios in sandbox before the cert call |
payabli-mcp-setup | Installs the official Payabli Docs MCP server |
Every skill above is live. New skills start with payabli-getting-started, which loads payabli-fundamentals and pulls in the rest as the work calls for them.
We're adding skills over time, so some Payabli capabilities don't have one yet — for example merchant boarding (onboarding merchants).
These skills are for building on Payabli, so you'll need a Payabli account with API access — that's where your sandbox credentials come from. Not a Payabli customer yet? Request a demo.
The skills steer your agent; you supply the credentials to test while building. To build and test against sandbox you'll need an organization ID and at least one entrypoint ID (a paypoint), plus a private API token (and a separate public token, if you mount embedded components in the browser). Read these from environment variables; never hardcode or commit the private token. A typical local .env:
# Payabli sandbox credentials. Copy into your app's local env file (e.g. .env.local),
# keep it gitignored, and never commit real values.
PAYABLI_BASE_URL=https://api-sandbox.payabli.com/api
PAYABLI_API_TOKEN= # PRIVATE token — server-side only; never expose to the browser or commit
PAYABLI_ENTRYPOINT= # an entrypoint (paypoint) to target; needed by nearly every call
PAYABLI_ORGID= # organization ID — for org-scoped calls (e.g. notifications, reporting)
npx claudepluginhub payabli/integration-skills --plugin payabli-integrationsComprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Design fluency for frontend development. 1 skill with 23 commands (/impeccable polish, /impeccable audit, /impeccable critique, etc.) and curated anti-pattern detection.
UI/UX design intelligence. 67 styles, 161 palettes, 57 font pairings, 25 charts, 15 stacks (React, Next.js, Vue, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Nuxt, Jetpack Compose). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
Behavioral guidelines to reduce common LLM coding mistakes, derived from Andrej Karpathy's observations on LLM coding pitfalls