Update to Zuora Coding Agent

{
  "description": "Propose the right Zuora API approach for a business requirement",
  "included_files": [],
  "name": "zuora-api-design",
  "skill_md_contents": "---\nname: zuora-api-design\ndescription: Propose the right Zuora API approach for a business requirement\nargument-hint: <business requirement description>\nallowed-tools: [Read, Glob, Grep, Bash, Agent, mcp__zuora-mcp__zuora_codegen, mcp__zuora-mcp__ask_zuora, mcp__zuora-mcp__query_objects]\n---\n\nCodex-only path resolution: When an instruction refers to `${CLAUDE_PLUGIN_ROOT}`, treat it as the root of this installed plugin. In Codex, resolve that root as the ancestor directory containing `skills/`, `references/`, and `.codex-plugin/`.\n\n\nYou are designing a Zuora API integration approach. The user has described a business requirement. Your job is to propose which Zuora APIs, objects, and patterns to use — NOT to generate code yet.\n\n## Input\n\nThe user's business requirement: $ARGUMENTS\n\n## Tool routing\n\nUse `mcp__zuora-mcp__zuora_codegen` for endpoint discovery, request/response schemas, fields, enum values, SDK method details, and API-specific constraints. Use bundled references for integration patterns and general best practices. Use `mcp__zuora-mcp__ask_zuora` only if a product-behavior or business-process question remains after those sources are checked.\n\n## Workflow\n\n### Step 1: Clarify the requirement\n\nIf the user's description is ambiguous, ask targeted questions:\n- What business outcome are they trying to achieve?\n- What system is calling Zuora (backend service, frontend, batch job)?\n- What Zuora objects are involved (accounts, subscriptions, invoices, payments)?\n- What is the expected data volume and frequency?\n- What programming language will be used?\n\n### Step 2: Discover relevant APIs\n\nCall `mcp__zuora-mcp__zuora_codegen` in this order:\n1. `code_guidance` with language (default to `curl` if unknown) — understand SDK capabilities\n2. `list_api_classes` — find relevant API groups\n3. `get_class_apis` for the most relevant class(es) — see available endpoints\n4. `get_api_details` for the most relevant endpoint(s) — get parameters, request/response shapes\n\n### Step 3: Clarify domain questions\n\nCall `mcp__zuora-mcp__ask_zuora` for unresolved product-level questions about Zuora Billing, Revenue, CPQ, or Payments behavior. Prefer checking endpoint specs (Step 2) and reference patterns (Step 5) first when they are likely to have the answer, but don't delay if the question is clearly qualitative. Skip this step when specs and references are sufficient.\n\n### Step 4: Check existing data model\n\nIf the user has a connected Zuora tenant, use `mcp__zuora-mcp__query_objects` to inspect existing objects (accounts, subscriptions, products) and validate assumptions about the data model.\n\n### Step 5: Read reference patterns\n\nRead `${CLAUDE_PLUGIN_ROOT}/references/api-integration-patterns.md` for common patterns and anti-patterns. Read `${CLAUDE_PLUGIN_ROOT}/references/best-practices.md` for integration best practices.\n\n### Step 6: Propose the design\n\nDeliver a structured response:\n\n- **Recommended APIs**: List of endpoints with purpose and HTTP method\n- **Object model**: Which Zuora objects are read/written and their relationships\n- **Call sequencing**: Order of API calls, dependencies, and data flow\n- **Authentication**: OAuth client credentials approach, token caching\n- **Error handling**: Retry strategy, idempotency, STOP_AND_CONFIRM handling\n- **Pagination**: How to handle paginated responses (if listing/querying)\n- **Risks and tradeoffs**: Rate limits, eventual consistency, known gotchas\n- **Next step**: Suggest using `/zuora-api-build` to generate implementation code\n\nDo NOT generate implementation code in this skill. Focus on design and approach selection.\n"
}