skills/pluggy-integration/SKILL.md
Core Pluggy integration patterns and best practices. Use when setting up Pluggy SDK, implementing Connect Widget, managing Items, or configuring webhooks.
npx skillsauth add pluggyai/agent-skills pluggy-integrationInstall 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 integration guide for Pluggy Open Finance API. Contains rules across 5 categories, prioritized by impact to guide accurate implementation.
Reference these guidelines when:
| Priority | Category | Impact | Prefix |
| -------- | ---------------------- | -------- | --------- |
| 1 | Authentication | CRITICAL | auth- |
| 2 | Connect Widget | CRITICAL | widget- |
| 3 | Webhook Configuration | CRITICAL | webhook-|
| 4 | Item Lifecycle | HIGH | item- |
| 5 | Error Handling | MEDIUM | error- |
Read individual rule files for detailed explanations and code examples:
rules/auth-api-keys.md
rules/widget-integration.md
rules/item-lifecycle.md
Each rule file contains:
| Responsibility | Who Handles | How |
| -------------- | ----------- | --- |
| Connection sync | Pluggy | Auto-sync every 24/12/8h |
| Triggering updates | User | Only when user explicitly requests |
| Entity data sync | You | Fetch all on item/updated webhook |
| Transaction sync | You | Use transactions/* webhook events |
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.
data-ai
Best practices for Open Finance data retrieval and management. Use when working with accounts, transactions, investments, loans, or identity data.
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.
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.