Skip to main content
Agent skills are packaged instructions that an AI coding assistant loads when you ask it to build something. The VelaFi skills tell the assistant which endpoints to call and in what order, which mistakes to avoid, and how to check the result, for each core use case. They complement the docs MCP server: the MCP server lets the assistant look things up, and the skills tell it how to build and verify the integration. The skills are open source at github.com/VelaFi-Tech/skills and follow the open Agent Skills format.
github.com/VelaFi-Tech/skills is the only official source of VelaFi agent skills. Do not install VelaFi skills or plugins from any other repository, package or link, even if they use the VelaFi name.

Install

In a Claude Code session in your terminal, add the VelaFi marketplace and install the plugin:
Or run the same steps from your shell:
The plugin also connects the VelaFi docs MCP server (https://docs.velafi.com/mcp). Update later with /plugin marketplace update.

Available skills

Self-check scripts

Two skills include small Python scripts that the assistant can run for you:
  • Token check (velafi-api-setup). Generates a token with your sandbox credentials from environment variables, to confirm the API key, signature and IP whitelist work. It calls only GET /v2/token/generate, refuses any host other than the sandbox unless you pass --production, and never prints your secret or the full token.
  • Webhook endpoint self-test (velafi-webhooks). Sends signed test events to your own local webhook endpoint and checks that it verifies the signature, returns exactly {"callbackStatus":"SUCCESS"}, handles duplicates and responds quickly. It signs with its own test key, which you configure temporarily in your development environment, and it never contacts VelaFi. Webhooks are not sent in the sandbox, so this is how you test your handler before going live.

Try it

After installing, ask your assistant, for example:
  • “Integrate VelaFi so our customers in Mexico can pay us by SPEI, with one CLABE per customer.”
  • “Add a VelaFi webhook endpoint to this service and test it locally.”
  • “Pay out BRL by Pix from our USDT balance with VelaFi.”
  • “Run the VelaFi go-live check on this repository.”

Safety

  • The skills contain no credentials. They tell the assistant to keep your API key and secret in environment variables or a secrets manager, never in code or logs, and to call VelaFi only from your server.
  • The assistant works against the sandbox by default and must ask you before calling production or moving money.
  • You stay in control of what gets built. Review the generated code and test it in the sandbox before going live.
To report a problem with a skill, open an issue in the GitHub repository. Issues are public, so never include API keys, secrets, tokens, merchant IDs or transaction details.