Integrate with AI coding assistants

What the skill is

A skill is a folder with a SKILL.md file that the AI assistant loads when a task matches its description. Wealth Reader publishes one in the open Agent Skills format, under the MIT license, in the public repository https://github.com/Wealth-Reader/wealthreader-skills.

The wealthreader-integration skill covers:

• The widget integration and the backend callback.
• Redirect authentication (OAuth) for native apps.
• Data refresh with the connection token and error handling.

It does not cover payment initiation or bank connector development. It does not replace customer onboarding either: you still need your api_key, the authorized domain, and the callback URL configured in the client area.

The same folder works in Claude Code, Codex, Cursor, Antigravity, Gemini CLI, GitHub Copilot, Grok Build, Windsurf, OpenCode, Amp, Cline, Roo Code, Kiro, and any other AI assistant that reads SKILL.md.

One-command install

npx skills add Wealth-Reader/wealthreader-skills

The installer detects the assistants you have and lets you choose where to copy the skill. You can also use your tool's own installer:

# GitHub CLI
gh skill install Wealth-Reader/wealthreader-skills wealthreader-integration --agent claude-code --scope user

# Gemini CLI
gemini skills install https://github.com/Wealth-Reader/wealthreader-skills.git --consent

# Amp
amp skill add https://github.com/Wealth-Reader/wealthreader-skills --global

Manual install

Copy the repository folder skills/wealthreader-integration/ into the directory your AI assistant reads, then open a new session. .agents/skills/ (project) and ~/.agents/skills/ (user) are the shared paths most AI assistants read. Claude Code, Cline, and Kiro read only their own directory.

Paths were checked against each tool's public documentation on 5 September 2026. The up-to-date table always lives in the repository README.

How to use it

Ask for the integration in your application's own language and framework. An example request:

Use the wealthreader-integration skill to add the Wealth Reader widget and backend callback to my application. Retrieve accounts and transactions, and test locally without making live banking requests.

The skill guides the AI assistant through the contracts documented in this guide instead of improvising from other open banking or OAuth APIs. For each flow, read the matching page:

• Widget and callback: Iframe: frontend and Iframe: backend.
• Redirect: OAuth: backend.
• Data refresh and errors: the API reference and the error catalog.

What it checks and what it does not

• It generates local tests with synthetic data and with the widget test users (MOCKDATA, MOCKOTP, MOCKLOGINKO). It does not run live bank connections on its own.
• It verifies that the callback persists data before answering {"status":"ok"}, that postMessage events are filtered by origin, and that invalid credentials never enter a retry loop.
• It flags the production controls this documentation does not define, such as callback authenticity, instead of inventing them. Resolve them with Support before going live.

Maintenance

The skill is built only from public documentation and links the sources of every contract. If you spot a discrepancy with this guide, open an issue in the repository.