Best practices for Open Finance data retrieval and management. Use when working with accounts, transactions, investments, loans, or identity data.
Install
npx skills add https://github.com/pluggyai/agent-skills --skill pluggy-open-financeSKILL.md
Pluggy Open Finance
Comprehensive guide for retrieving and managing Open Finance data through Pluggy. Contains rules across 5 categories, prioritized by impact.
When to Apply
Reference these guidelines when:
- Selecting appropriate connectors for financial institutions
- Retrieving account balances and details
- Fetching and processing transactions
- Accessing investment portfolios and holdings
- Retrieving loan information
- Fetching user identity data
- Implementing data synchronization strategies
Rule Categories by Priority
| 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- |
How to Use
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:
- Brief explanation of why it matters
- Incorrect code example with explanation
- Correct code example with explanation
- Additional context and references
- Pluggy-specific notes
Data Products Available
| 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 |
Full Compiled Document
For the complete guide with all rules expanded: AGENTS.md
Related skills
entra-app-registrationmicrosoft606KGuides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.azure-messagingmicrosoft595KTroubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, servicentra-agent-idmicrosoft328KProvision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmi_path, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmi_path token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registsupabasesupabase298KUse when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); deb
