Christerlin

Heyqo Cards — Development skill for Claude Code

Development community

Claude Code skill for integrating HeyQo virtual Visa cards: what the live API actually does.

How to install Heyqo Cards

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Christerlin/heyqo-cards and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Heyqo Cards does

Claude Code skill for integrating HeyQo virtual Visa cards: what the live API actually does.

Alternatives in Development

  • QuickSilver OS — 📊 You are ChatGPT-4, running the QuickSilver OS, a user-friendly and powerful virtual operating system that e 9.1k ★
  • Gallery — Build a static, shareable gallery from your fidelity reports — an index of score cards plus a permalink page ( 3.6k ★
  • Sanitize — Detect and redact PII from text files — 15 categories (SSNs, credit cards, API keys, etc.), zero dependencies 3.1k ★

README

heyqo-cards

A [Claude Code](https://claude.com/claude-code) skill for integrating **HeyQo** virtual Visa cards.

Everything here was established against the live API. Their documentation does not describe most of it, and several field names are not what you would guess: the balance is `amount`, the card's details are nested under `info`, and card creation wants a different customer id than the one their listing puts first.

Written while taking a Haitian wallet from sandbox to production, so it covers more than response shapes: who owns the cardholder KYC, what a flat per-load fee does to pricing, and the rules that keep a ledger and an issuer from drifting apart.

Install

git clone https://github.com/Christerlin/heyqo-cards ~/.claude/skills/heyqo-cards

Claude Code picks it up on the next session.

What's in it

SKILL.md The mental model, the cost structure, the money-safety rules
references/api.md Endpoint by endpoint, field by field
references/secure-view.md The hosted page that shows the full card number

Using it outside Claude Code

The files are plain Markdown with no tooling in them, so nothing here is locked to one agent. Only the automatic triggering is: the `name` and `description` in `SKILL.md`'s frontmatter are what tells a Claude agent when to reach for this, and another tool will not read them.

Everywhere else, point at it or paste it:

  • Claude Code, the Claude Agent SDK, claude.ai: drop it in the skills directory and it loads itself when the work touches HeyQo.
  • Cursor, Copilot, Windsurf, anything else: AGENTS.md in this repo is read by several of them directly. Otherwise reference SKILL.md and the file under references/ that matches what you are doing, or copy the relevant section into whatever instruction file your tool uses.
  • A person: it is written to be read. Start with SKILL.md; the references are for when you are actually writing the request.