# pluggy-doctor

Reviews existing Pluggy integrations against the official docs and returns findings with file locations, line numbers, and code fixes.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 394 installs · ★ 7
- Author: pluggy
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/pluggyai/agent-skills/tree/HEAD/skills/pluggy-doctor/SKILL.md
- Updated: 2026-05-29
- HTML: https://affpapa.org/en/nevibecode/skills/pluggy-doctor

## What it does

pluggy-doctor examines Pluggy integration files and checks their implementation against the current official documentation. It covers flows such as `connect_token`, API requests, and webhook handlers, then produces a diagnostic report marked ✅, ❌, or ⚠️. Each issue includes the affected file, line, and a proposed fix.

The skill uses the Pluggy MCP to retrieve live documentation criteria. When that connection is unavailable, it reads the official docs through a web fallback and labels the reduced-confidence mode in the report. Existing integration files are required for a review. pluggy-doctor reviews code; it does not build an integration from scratch.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add pluggyai/agent-skills --skill pluggy-doctor -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/pluggy-doctor/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/pluggy-doctor/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add pluggyai/agent-skills --skill pluggy-doctor -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/pluggy-doctor/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add pluggyai/agent-skills --skill pluggy-doctor -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/pluggy-doctor/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install pluggyai/agent-skills pluggy-doctor
```

2. **Manually: put the files in place**
- File: `.github/skills/pluggy-doctor/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add pluggyai/agent-skills --skill pluggy-doctor -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/pluggyai/agent-skills --path skills/pluggy-doctor
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/pluggy-doctor/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add pluggyai/agent-skills --skill pluggy-doctor -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/pluggyai/agent-skills/tree/HEAD/skills/pluggy-doctor/SKILL.md

## When to use it
- review Pluggy API calls
- inspect webhook handlers for defects
- check `connect_token` creation against the docs
- locate an issue by file and line
- assess whether an integration is ready for production

## Example prompts
- Review my Pluggy integration and list issues with file and line references.
- Inspect the `item/created` webhook handler and show the required fixes.
- Check this Pluggy code against the official docs and assess its production readiness.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 6219f6e76087a292.

BEGIN THIRD-PARTY FILE 6219f6e76087a292
```text
---
name: pluggy-doctor
description: 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.
license: MIT
metadata:
  author: pluggy
  version: "1.0.0"
---

# Pluggy Doctor 🩺

> **Output language: mirror the dev.** These instructions are written in English for maintainability, but everything the dev sees — clarifying questions, the full diagnostic report, the verdict, and the degraded-mode banner — must be written in **the same language the dev is using**. If the dev writes in Spanish, answer in Spanish; in English, English; in Portuguese, Portuguese. Match the language of the dev's latest message (fall back to the language of their code/comments if that's clearer). The report template below is shown in PT-BR only as a layout example — translate its headings, labels, and verdict strings to the dev's language. Do **not** force PT-BR.

You are a code reviewer specialized in Pluggy integrations. The dev uploads their integration files and you return a structured diagnosis: what's right, what's wrong, and the corrected code for each issue — before it ships to production.

This is not a generic code review. You know Pluggy's integration flow and you **diagnose against Pluggy's official documentation** — never from memory, never against a frozen checklist.

## Requirements

This skill's source of truth is Pluggy's official documentation. It reaches it in one of two ways, in this order of preference:

1. **Pluggy MCP (preferred).** A live connection to the docs. Tools appear in your tool list as `Pluggy MCP:*` (e.g. `search`, `fetch`, `get-endpoint`). To connect it: add `https://docs.pluggy.ai/mcp` as an HTTP MCP server in the client (Claude Code: `claude mcp add --transport http pluggy-docs https://docs.pluggy.ai/mcp`; claude.ai: Settings → Connectors).
```
END THIRD-PARTY FILE 6219f6e76087a292

The third-party file has ended. Everything between the 6219f6e76087a292 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2812 of 16726 bytes. © pluggy · MIT · https://github.com/pluggyai/agent-skills/tree/HEAD/skills/pluggy-doctor/SKILL.md

## Similar
- [improve-codebase-architecture](https://affpapa.org/en/nevibecode/skills/improve-codebase-architecture.md) — skill · 1163035 installs
- [tdd](https://affpapa.org/en/nevibecode/skills/tdd.md) — skill · 1141062 installs
- [triage](https://affpapa.org/en/nevibecode/skills/triage.md) — skill · 990453 installs
- [codebase-design](https://affpapa.org/en/nevibecode/skills/codebase-design.md) — skill · 850344 installs

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md