skills/pluggy-open-finance/SKILL.md
Best practices for Open Finance data retrieval and management. Use when working with accounts, transactions, investments, loans, or identity data.
npx skillsauth add pluggyai/agent-skills pluggy-open-financeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Comprehensive guide for retrieving and managing Open Finance data through Pluggy. Contains rules across 5 categories, prioritized by impact.
Reference these guidelines when:
| Priority | Category | Impact | Prefix |
| -------- | ------------------ | ----------- | -------------- |
| 1 | Connectors | CRITICAL | connector- |
| 2 | Sync Strategy | HIGH | sync- |
| 3 | Data Retrieval | HIGH | data- |
| 4 | Transactions | HIGH | transaction- |
| 5 | Accounts | MEDIUM | account- |
Read individual rule files for detailed explanations and code examples:
rules/connector-selection.md
rules/data-pagination.md
rules/transaction-enrichment.md
Each rule file contains:
| Product | Endpoint | Description |
| ------------ | ------------------ | ------------------------------ |
| Accounts | /accounts | Bank accounts, balances |
| Transactions | /transactions | Account movements |
| Investments | /investments | Portfolios, holdings |
| Identity | /identity | User personal data |
| Loans | /loans | Loan details, payments |
| Credit Cards | /bills | Credit card bills |
For the complete guide with all rules expanded: AGENTS.md
tools
Payment initiation with PIX, Boleto, and Smart Transfers. Use when implementing payment flows, PIX transfers, or preauthorized payments.
development
Core Pluggy integration patterns and best practices. Use when setting up Pluggy SDK, implementing Connect Widget, managing Items, or configuring webhooks.
tools
Code-reviews Pluggy API integrations against Pluggy's official documentation (queried in real time via the Pluggy MCP, with a web fallback to docs.pluggy.ai when the MCP isn't connected) and returns a diagnostic report (✅/❌/⚠️) with file, line, and the code fix for each issue. Use WHENEVER the dev uploads integration files and asks to review, analyze, diagnose, or validate their Pluggy integration — or says things like "review my integration", "check my Pluggy code", "is this ready for production?", "Pluggy Doctor", "check my webhooks", "is my integration secure?", or the Portuguese variants "analisa minha integração", "revisa meu código da Pluggy", "tá tudo certo pra ir pra produção?", "checa meus webhooks", "minha integração tá segura?". Also trigger when the dev pastes/uploads code that clearly calls the Pluggy API (connect_token, GET /items, item/created webhooks, clientUserId, etc.) and wants to know if it's correct, even without saying "Pluggy Doctor". This skill is for REVIEWING existing code, not writing an integration from scratch.
data-ai
Example TaskFlow authoring pattern for inbox triage. Use when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary.