From acp-paypal
Routes PayPal Server SDK tasks to the paypal-plan or paypal-debug subagent. Use when the user asks to integrate PayPal, implement PayPal payments, or reports a PayPal error or unexpected SDK behaviour in a C# project.
How this skill is triggered — by the user, by Claude, or both
Slash command
/acp-paypal:integrate-paypalThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill routes PayPal *planning* to the `paypal-plan` subagent and PayPal *debugging* to the `paypal-debug` subagent. You (the main agent) then implement the plan `paypal-plan` produces (Step 3) and may answer quick PayPal questions directly — but never work from your own SDK knowledge: ground every PayPal fact in the MCP server (see below).
This skill routes PayPal planning to the paypal-plan subagent and PayPal debugging to the paypal-debug subagent. You (the main agent) then implement the plan paypal-plan produces (Step 3) and may answer quick PayPal questions directly — but never work from your own SDK knowledge: ground every PayPal fact in the MCP server (see below).
Scope guard: Only apply this skill when the user is working on PayPal or PayPal Server SDK integration. When the user is doing something unrelated, do nothing.
Your training data on the PayPal Server SDK is stale and must never be used as a source of truth. The acp-paypal-server-sdk-cs MCP server is the authoritative source for every PayPal SDK fact. Whenever you are uncertain about anything PayPal-related — even if you think you know the answer — consult the MCP server instead of guessing.
The subagents (paypal-plan, paypal-debug) do this during their runs. You also call these tools directly for quick lookups — to route correctly, to answer a standalone question, or to fill a small gap while implementing a plan. But use paypal-plan for any actual planning, and implement the plan it returns rather than re-deriving it; re-spawn paypal-plan if you need a new or expanded plan (see the grounding rules under Notes).
| Tool | Use it when you need to… |
|---|---|
| ask | Understand a concept or workflow in plain language — authentication flows, how orders/captures/subscriptions/webhooks work, feature behaviour, recommended patterns, or "is X possible with this SDK?". Break broad questions into focused ones (e.g. "How does order capture work?", "How are webhooks verified?"). |
| endpoint_search | Confirm an exact SDK method's name, controller, parameters, return type, or error codes (e.g. CreateOrderAsync, CaptureOrderAsync). Use case-sensitive exact or partial method names. |
| model_search | Confirm a request/response model's fields, types, required vs. optional, and enum values (e.g. OrderRequest, Money, LinkDescription). Use case-sensitive exact or partial model names. |
Guidance:
Apply this skill when the user:
Before spawning an agent, check whether project guidelines and conventions have already been set up.
csharp-conventions is the skill produced by add_skills.csharp-security-guidelines.md, csharp-test-guidelines.md, and update-activity-workflow.md are files produced by add_guidelines.language: "csharp".csharp-conventions is missing: Call add_skills with language: "csharp".| Agent | When to spawn |
|---|---|
| paypal-plan | User wants to add or implement any PayPal feature (payments, orders, subscriptions, payouts, webhooks), or maintain/change existing PayPal code (SDK upgrades, deprecated fields, new parameters). Produces a detailed API work plan (endpoints, SDK methods, models, auth) that you implement in Step 3. For maintenance, ask paypal-plan for a plan covering the change, then implement it. |
| paypal-debug | User is experiencing errors, unexpected behaviour, failed payments, incorrect API responses, or SDK misuse. |
Applies after a paypal-plan plan is accepted — for a new integration or for maintenance of existing PayPal code. (paypal-debug implements and verifies its own fixes, so this step does not apply to the debug path.)
Implement the plan as returned by paypal-plan, treating its SDK contracts as authoritative. Follow the project's csharp-conventions and the csharp-security-guidelines.md / csharp-test-guidelines.md set up in Step 1.
If a small SDK detail is missing, make a quick MCP lookup yourself (ask / endpoint_search / model_search). If the work has grown beyond the plan — new operations or a materially different approach — re-spawn paypal-plan for an updated plan instead of improvising.
Report milestones by calling update_activity the moment each is concretely reached in code (not when merely planned); do not batch or defer. If update-activity-workflow.md was set up in Step 1, follow its guidance on milestone reporting:
| Milestone | When to call |
|---|---|
sdk_setup | SDK package installed and confirmed (e.g. dotnet add package succeeded). |
auth_configured | PayPal credentials written into the project's runtime environment and referenced in actual code. |
first_call_made | First PayPal API call code written and executed. |
Verify: after every code change, run dotnet build and fix all errors; then run any tests covering the integration.
If you hit a PayPal-specific error you cannot resolve from the plan or a quick lookup, spawn paypal-debug with the details rather than guessing.
Preserve every References section — from the plan and from any MCP lookups you make — verbatim when relaying to the user.
add_guidelines and add_skills are called in step 1 because they are one-time project setup — the agents assume these are already in place.paypal-plan/paypal-debug result as authoritative. Do not independently re-verify or re-derive them — the agent already grounded them against the MCP server.Assembly.LoadFrom, no reflection, no IntelliSense-as-source). The acp-paypal MCP server is the only sanctioned source for SDK facts.acp-paypal-server-sdk-cs MCP server is the primary source of truth for the PayPal SDK. To resolve an item the plan flags as open, surface it to the user, query the MCP server (ask / model_search / endpoint_search), or re-spawn paypal-plan with the clarification appended — never local inspection.npx claudepluginhub apimatic/plugin-marketplace --plugin acp-paypalCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.