Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -148,7 +148,7 @@ Each supported language ships the same eight:
The `getting-started` skill is the entry point: it directs the agent to clone and grep the real SDK
source, so every fact is grounded in the actual contract rather than model knowledge.

Across the marketplace that's **<!-- BEGIN:LANGUAGE_PACK_COUNT -->91<!-- END:LANGUAGE_PACK_COUNT --> language packs and <!-- BEGIN:SKILL_COUNT -->887<!-- END:SKILL_COUNT --> skills**. See
Across the marketplace that's **<!-- BEGIN:LANGUAGE_PACK_COUNT -->91<!-- END:LANGUAGE_PACK_COUNT --> language packs and <!-- BEGIN:SKILL_COUNT -->890<!-- END:SKILL_COUNT --> skills**. See
[`plugins/paypal/README.md`](plugins/paypal/README.md) for a worked example.

## Repository structure
Expand Down
7 changes: 5 additions & 2 deletions plugins/plaid/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
{
"name": "plaid",
"displayName": "The Plaid API",
"version": "0.2.0",
"description": "Integrate and consume the APIMatic-generated The Plaid API SDK — bundled skills for C#/.NET, python, TypeScript.",
"version": "0.2.1",
"description": "Integrate and consume the APIMatic-generated The Plaid API SDK — bundled skills for C#/.NET, Python, TypeScript.",
"author": {
"name": "APIMatic",
"email": "developer@apimatic.io"
Expand All @@ -14,5 +14,8 @@
"./skills/dotnet",
"./skills/python",
"./skills/typescript"
],
"agents": [
"./scoped/agents/the-plaid-api-planner.md"
]
}
10 changes: 10 additions & 0 deletions plugins/plaid/.codex-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
{
"name": "plaid",
"version": "0.2.1",
"description": "Integrate and consume the APIMatic-generated The Plaid API SDK — bundled skills for C#/.NET, Python, TypeScript.",
"skills": "./skills",
"interface": {
"displayName": "The Plaid API",
"developerName": "APIMatic"
}
}
4 changes: 2 additions & 2 deletions plugins/plaid/.cursor-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
{
"name": "plaid",
"displayName": "The Plaid API",
"version": "0.2.0",
"description": "Integrate and consume the APIMatic-generated The Plaid API SDK — bundled skills for C#/.NET, python, TypeScript.",
"version": "0.2.1",
"description": "Integrate and consume the APIMatic-generated The Plaid API SDK — bundled skills for C#/.NET, Python, TypeScript.",
"author": {
"name": "APIMatic",
"email": "developer@apimatic.io"
Expand Down
17 changes: 14 additions & 3 deletions plugins/plaid/README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# The Plaid API SDK Plugin

A plugin whose skills teach a coding agent to install and use the APIMatic-generated **The Plaid API SDK**, in C#/.NET, python, TypeScript. Every SDK fact the skills state is grounded in the SDK's own source and generated documentation, not in what a model remembers about this API.
A plugin whose skills teach a coding agent to install and use the APIMatic-generated **The Plaid API SDK**, in C#/.NET, Python, TypeScript. Every SDK fact the skills state is grounded in the SDK's own source and generated documentation, not in what a model remembers about this API.

## What's inside

Expand All @@ -9,5 +9,16 @@ One skill set per language. The entry point is that language's getting-started s
| Language | Skill prefix | Skills |
| --- | --- | --- |
| C#/.NET | `dotnet-` | `dotnet-authentication`, `dotnet-calling-endpoints`, `dotnet-client-initialization`, `dotnet-configuration-resilience`, `dotnet-error-handling`, `dotnet-getting-started`, `dotnet-integrate-the-plaid-api`, `dotnet-models`, `dotnet-testing` |
| python | `python-` | `python-authentication`, `python-calling-endpoints`, `python-client-initialization`, `python-configuration-resilience`, `python-error-handling`, `python-getting-started`, `python-integrate-the-plaid-api`, `python-models`, `python-testing` |
| TypeScript | `typescript-` | `typescript-authentication`, `typescript-calling-endpoints`, `typescript-client-initialization`, `typescript-configuration-resilience`, `typescript-error-handling`, `typescript-getting-started`, `typescript-integrate-the-plaid-api`, `typescript-models`, `typescript-testing` |
| Python | `python-` | `python-authentication`, `python-calling-endpoints`, `python-client-initialization`, `python-configuration-resilience`, `python-error-handling`, `python-event-streams`, `python-file-handling`, `python-getting-started`, `python-integrate-the-plaid-api`, `python-models`, `python-testing` |
| TypeScript | `typescript-` | `typescript-authentication`, `typescript-calling-endpoints`, `typescript-client-initialization`, `typescript-configuration-resilience`, `typescript-error-handling`, `typescript-event-streams`, `typescript-getting-started`, `typescript-integrate-the-plaid-api`, `typescript-models`, `typescript-testing` |

## Agents

| Agent | What it does |
| --- | --- |
| `the-plaid-api-planner` | Writes `the-plaid-api-plan.md`, the plan and its contract sheet, before any project code is written, and revises it in place. `dotnet-integrate-the-plaid-api`, `typescript-integrate-the-plaid-api` and `python-integrate-the-plaid-api` each start it once the SDK is installed or its source reached, on the main agent's own model. |

How each host gets it:

- **Claude Code** loads it from `scoped/agents/` with the plugin and lists it as `plaid:the-plaid-api-planner`. Its file sets `model: inherit`, so it runs on the main agent's model.
- **Where no subagent tool lists it** (a host that doesn't load a plugin's agents, or subagents turned off), the main agent says so in one line and writes the plan itself before any code.
4 changes: 2 additions & 2 deletions plugins/plaid/plugin.json
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
{
"name": "plaid",
"displayName": "The Plaid API",
"version": "0.2.0",
"description": "Integrate and consume the APIMatic-generated The Plaid API SDK — bundled skills for C#/.NET, python, TypeScript.",
"version": "0.2.1",
"description": "Integrate and consume the APIMatic-generated The Plaid API SDK — bundled skills for C#/.NET, Python, TypeScript.",
"author": {
"name": "APIMatic",
"email": "developer@apimatic.io"
Expand Down
21 changes: 21 additions & 0 deletions plugins/plaid/scoped/agents/the-plaid-api-planner.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
---
name: "the-plaid-api-planner"
description: "The The Plaid API planner. It writes the-plaid-api-plan.md, the plan and its map-grounded contract sheet, before any project code is written, and revises it in place when the main agent sends a clarification. Main agent: start it when an integrate skill of this plugin tells you to, once per integration, with the user's whole request, the name of the integrate skill you loaded, the absolute project root and the absolute path to write the-plaid-api-plan.md to, plus the SDK source's path where that skill says to pass it; edit no project file until it has returned and you have read that file; send revisions to the same agent rather than starting a second."
model: "inherit"
tools: "Read, Grep, Skill, Write, Edit, Bash"
---

You are the The Plaid API planner. You write `the-plaid-api-plan.md` — the plan and its contract sheet — before any project code is written, and you revise it when the main agent sends a clarification. You never write or fix project code, and you never start another agent: you are the planner the workflow asks for.

**Your instructions are the integrate skill your task names** — this plugin's `<language>-integrate-the-plaid-api` skill for the project's language. Load it, and the getting-started skill it has you load first. Your job is everything that skill puts in `the-plaid-api-plan.md`: the plan, its contract sheet and every table and block the sheet carries, wherever the skill describes them, grounded exactly as the skill says. Skip what belongs to the main agent: *The planner agent* (you are that agent), the read-only prerequisites, the required reading it does before implementing, and the implementation itself. Where your task gives the path of the SDK source the main agent reached, read the map and the source there; reach the SDK source yourself only when it gives none.

## Plan mode

Your task gives you the user's whole request, the integrate skill to follow, the absolute project root, the absolute path to write to and, where the integrate skill has the main agent reach the SDK source first, the absolute path to it. Write `the-plaid-api-plan.md` at exactly the path to write to; if none was given, use `<project repo root>/the-plaid-api-plan.md` and say so when you return. It is the only project file you write. Read the project's code only where a table needs it, such as where the codebase already keeps its records, and only read it: do not edit project code, install anything into the project, or run its build or tests.

Return the plan's path, a one-paragraph summary, and its **Assumptions & Blockers** section verbatim.

## Revision mode

When the main agent sends a clarification, a correction or a gap, revise `the-plaid-api-plan.md` in place with targeted edits — edit the changed rows, append a new section; never rewrite the whole file to change a few rows. Reply with ONLY the changed or added rows, verbatim, plus one sentence of context: the main agent works from your reply and does not re-read the file.

Loading
Loading